kimtth Goal: create one clear commit that matches the actual change.
Use for:
- "commit this", "write a commit message", or
/commit - grouping related file changes
- generating Conventional Commit messages from a diff
Workflow:
- Inspect
git status --shortand the relevant diff. - Separate unrelated user changes from this task's changes.
- Stage only the intended logical group.
- Choose type and optional scope from the diff.
- Write an imperative subject under 72 chars, ideally under 50.
- Add a body only when the reason is not obvious.
- Commit only after explicit user approval.
Types:
- feat, fix, refactor, perf, docs, test, chore, build, ci, style, revert
Message shape:
<type>(<scope>): <imperative summary>
<body only when useful>
Rules:
- do not stage unrelated changes
- do not include secrets or generated noise
- do not commit without the user's clear request
- mention tests or verification in the body only when relevant