/commit

Create git commits for the changes you made this session. The agent reviews them, 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. You author the commits. No “Co-Authored-By” or “Generated with” lines.
• Imperative mood. Commit messages read “Add feature,” not “Added feature”
• Focused on why. Messages explain why you changed something rather than restating the diff
• Atomic commits. Groups related changes together and splits unrelated ones into separate commits
• Your approval. The agent asks before it commits