/commit

Create git commits for changes made during the current session. The agent reviews changes, groups related files, drafts commit messages, and asks for confirmation.

Usage

/commit

Process

1. Review changes — Runs git status and git diff to understand what changed
2. Plan commits — Groups related files and drafts commit messages
3. Present plan — Shows the proposed commits and asks for confirmation
4. Execute — Uses git add with specific files (never -A or .) and creates commits

Key Behavior

• No attribution — Commits are authored solely by you. No “Co-Authored-By” or “Generated with” lines.
• Imperative mood — Commit messages use imperative mood (“Add feature” not “Added feature”)
• Focused on why — Messages explain why changes were made, not just what changed
• Atomic commits — Groups related changes together, splits unrelated changes into separate commits
• User approval — Always asks before committing

What This Adds

All three base tools can run git commands, but they don’t have opinions about how to use git. They’ll commit everything with git add ., write generic commit messages, and add “Co-Authored-By” attribution lines.

/commit encodes specific constraints: no AI attribution (no “Co-Authored-By,” no “Generated with,” no “AI-assisted”), imperative mood messages focused on the “why” not the “what,” specific git add paths (never -A or .), and mandatory user approval before executing. These are things you’d have to type out every time in a direct conversation, and they’d drift or get forgotten within a few exchanges.