commit 6a57ba2a3a6b08816ac78b997870bc90a3c2ee58
parent 7fe5b84aee85ab0abee7946e30a45c74100fb66b
Author: minerva-jupiter <ryouturn@gmail.com>
Date: Fri, 5 Jun 2026 16:49:11 +0900
feat(settings): configure agent servers and terminal shell
Add Gemini agent registry and set nu.exe as the default terminal shell.
Diffstat:
2 files changed, 34 insertions(+), 0 deletions(-)
diff --git a/AGENTS.md b/AGENTS.md
@@ -0,0 +1,24 @@
+## Commit message
+
+You are an expert at writing Git commits. Your job is to write a short clear commit message that summarizes the changes.
+
+If you can accurately express the change in just the subject line, don't include anything in the message body. Only use the body when it is providing *useful* information.
+
+Don't repeat information from the subject line in the message body.
+
+Only return the commit message in your response. Do not include any additional meta-commentary about the task. Do not include the raw diff output in the commit message.
+
+Follow good Git style:
+
+- Separate the subject from the body with a blank line
+- Try to limit the subject line to 50 characters
+- Capitalize the subject line
+- Do not end the subject line with any punctuation
+- Use the imperative mood in the subject line
+- Wrap the body at 72 characters
+- Keep the body short and concise (omit it entirely if not useful)
+
+## Name Rule
+
+Function and variable names should be concise and clearly indicate their function.
+In particular, names that are relative to the timeline and unrelated to the program's semantics, such as "Fixed," are strictly prohibited.
diff --git a/settings.json b/settings.json
@@ -7,6 +7,16 @@
// custom settings, run `zed: open default settings` from the
// command palette (cmd-shift-p / ctrl-shift-p)
{
+ "agent_servers": {
+ "gemini": {
+ "type": "registry"
+ }
+ },
+ "terminal": {
+ "shell": {
+ "program": "nu.exe"
+ }
+ },
"outline_panel": {
"dock": "left",
},
