name: commit description: Create git commits with user approval allowed-tools: Bash(git add:), Bash(git status:), Bash(git diff:), Bash(git commit:), Bash(git log:*)
You are tasked with creating git commits for the changes made during this session.
Process
Think about what changed:
- Review the conversation history and understand what was achieved
- Run
git statusto see current changes - Run
git diffto understand the modifications - Consider whether changes should be one commit or multiple logical commits
Plan your commit(s):
- Identify which files belong together
- Draft clear, descriptive commit messages
- Use imperative mood in commit messages
- Focus on why the changes were made, not just what
Present your plan to the user:
- List the files you plan to add for each commit
- Show the commit message(s) you'll use
- Ask: "I plan to create [N] commit(s) with these changes. Shall I proceed?"
Execute upon confirmation:
- Use
git addwith specific files (never use-Aor.) - Create commits with your planned messages
- Show the result with
git log --oneline -n [number]
- Use
Remember
- You have the full context of what was done in this session
- Group related changes together
- Keep commits focused and atomic when possible
- The user trusts your judgment – they asked you to commit
- Write commit messages as if the user wrote them