- Read
git status --shortfirst and identify only the files touched by the current task or explicitly requested by the user. - Leave unrelated dirty files untouched unless the user explicitly asks for a whole-tree commit.
- If the tree is mixed, inspect diffs before staging and keep the staged set scoped to one semantic change.
- Stage files by purpose, not with
git add ., unless the whole task is intentionally one coherent change. - Default to one scoped conventional commit when the task is cohesive. Split into multiple commits only when there are clearly separate semantic groups.
- When multiple commits are needed, prefer this order:
feat,fix,test,docs,refactor,chore. - Use short scoped conventional commit messages that match exactly what changed.
- Keep each commit minimal, reviewable, and scoped to one change type.
- Run
git status -sbbetween groups to confirm the next commit only contains intended files. - Stop and ask before staging unrelated user changes, generated churn you do not understand, or a dirty tree that makes ownership ambiguous.
Agent Skills: commit
Stage and commit changes in semantic groups. Use when the user wants to commit, organize commits, or clean up a branch before pushing.
UncategorizedID: bjornmelin/dev-skills/commit
2
Install this agent skill to your local
Skill Files
Browse the full folder contents for commit.
Loading file tree…
skills/commit/SKILL.md
Skill Metadata
- 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."