commit ยท diff
git:20260308.795c15b to git:20260418.43348ae
11 added, 11 removed. Audit A to A.
---
name: "commit"
- description: "Stage and commit changes in semantic groups. Use when the user wants to commit, organize commits, or clean up a branch before pushing."
+ description: "Stage + commit changes in semantic + reviewablegroups. Use when user wants to commit changes, organize commits, or clean up a branch before pushing."
---
- 1. Read `git status --short` first and identify only the files touched by the current task or explicitly requested by the user.
- 2. Leave unrelated dirty files untouched unless the user explicitly asks for a whole-tree commit.
- 3. If the tree is mixed, inspect diffs before staging and keep the staged set scoped to one semantic change.
- 4. Stage files by purpose, not with `git add .`, unless the whole task is intentionally one coherent change.
- 5. Default to one scoped conventional commit when the task is cohesive. Split into multiple commits only when there are clearly separate semantic groups.
- 6. When multiple commits are needed, prefer this order: `feat`, `fix`, `test`, `docs`, `refactor`, `chore`.
- 7. Use short scoped conventional commit messages that match exactly what changed.
- 8. Keep each commit minimal, reviewable, and scoped to one change type.
- 9. Run `git status -sb` between groups to confirm the next commit only contains intended files.
- 10. Stop and ask before staging unrelated user changes, generated churn you do not understand, or a dirty tree that makes ownership ambiguous.
+ 1. `git status --short` first; scope to files from current task or explicit user request.
+ 2. Leave unrelated dirty files alone unless user explicitly asks for a whole-tree commit.
+ 3. Mixed tree: inspect diffs before staging; keep staged set one semantic change.
+ 4. Stage by purpose, not `git add .`, unless whole task one coherent change.
+ 5. Default one scoped conventional commit when task cohesive. Split only for clearly separate semantic groups. Optimize for reviewability.
+ 6. Multiple commits: prefer order `feat`, `fix`, `test`, `docs`, `refactor`, `chore`.
+ 7. Short scoped conventional messages; match what changed.
+ 8. Each commit minimal, reviewable, one change type.
+ 9. Between groups: `git status -sb`; confirm next commit has only intended files.
+ 10. Ask before staging unrelated user changes, unfamiliar generated churn, or ambiguous dirty tree that makes ownership ambiguous.