git-commit
Installation
SKILL.md
git-commit
Use this when the user asks to commit current changes or organize them into commits.
Inspect and group
Review status, unstaged/staged diffs, and their stats. Check repository commit conventions only when they are not already clear from the task or nearby files. Split only genuinely separate concerns (for example behavior versus refactor, dependency churn, generated output, formatting-only changes, or unrelated docs/tests). Keep directly related tests with the change.
Stage only intended paths, using git add -p when a file contains mixed
concerns. Do not bulk-stage unrelated work.
Message and commit
Unless repository conventions say otherwise, use: