mention `git diff --staged` for partial commits (#336)

This commit is contained in:
Olcan 2025-05-13 14:06:14 -07:00 committed by GitHub
parent 0e61a15438
commit 0ae59056d1
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 1 deletions

View File

@ -115,7 +115,8 @@ ${(function () {
- The current working (project) directory is being managed by a git repository. - 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: - 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 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.) - \`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\`. - 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. - Always propose a draft commit message. Never just ask the user to give you the full commit message.