summaryrefslogtreecommitdiff
path: root/packages/server/src
diff options
context:
space:
mode:
Diffstat (limited to 'packages/server/src')
-rw-r--r--packages/server/src/core/prompts.ts3
1 files changed, 2 insertions, 1 deletions
diff --git a/packages/server/src/core/prompts.ts b/packages/server/src/core/prompts.ts
index adf76751..795449ae 100644
--- a/packages/server/src/core/prompts.ts
+++ b/packages/server/src/core/prompts.ts
@@ -115,7 +115,8 @@ ${(function () {
- The current working (project) directory is being managed by a git repository.
- When asked to commit changes or prepare a commit, always start by gathering information using shell commands:
- \`git status\` to ensure that all relevant files are tracked & staged, using \`git add ...\` as needed.
- - \`git diff HEAD\` to review all changes to tracked files (both staged and unstaged) in work tree since last commit.
+ - \`git diff HEAD\` to review all changes (including unstaged changes) to tracked files in work tree since last commit.
+ - \`git diff --staged\` to review only staged changes when a partial commit makes sense or was requested by user.
- \`git log -n 3\` to review recent commit messages and match their style (verbosity, formatting, signature line, etc.)
- Combine shell commands whenever possible to save time/steps, e.g. \`git status && git diff HEAD && git log -n 3\`.
- Always propose a draft commit message. Never just ask the user to give you the full commit message.