| name | git-commit |
| description | Use when preparing clean, logical git commits from an existing working tree |
Git Commit
Prepare focused commits that are easy to review and revert.
Workflow
- Load
git-best-practices.
- Inspect
git status, staged changes, unstaged changes, current branch, and recent commits.
- Group changes by intent, not by file extension.
- Stage only the files for one logical commit at a time.
- Use a conventional commit subject when it fits the repo style.
- Run the relevant verifier before committing when the change is non-trivial.
Rules
- Never include unrelated drift just because it is present.
- Do not rewrite or discard user changes unless explicitly asked.
- If the tree contains multiple unrelated changes, create multiple commits.
- Mention uncommitted leftovers after committing.
- If the human will review the working tree in hunk, write the
.hunk/agent-context.json
sidecar before committing (see hunk-notes), and keep .hunk/ out of the commit.