commit
Installation
SKILL.md
Git Commit
Group all unstaged/untracked changes into atomic commits — one commit per logical concern. A single concern is just the degenerate case: one commit. Never push — pushing belongs to /hb:to-pr.
Paths in $ARGUMENTS scope the run: commit only those files and leave the rest of the tree as it is.
Message style
Match the repo's existing commit patterns from git log. Extreme concision — sacrifice grammar for brevity. Focus on "why" not "what". Imperative mood. Conventional commits (feat/fix/refactor/docs/chore + scope) when the repo uses them.
Workflow
- Review full diff and status; read recent log for style.
- Identify logical groups: feature/fix, its tests, config, formatting-only, docs, assets.
- Per group: stage those files explicitly by name, commit with a HEREDOC message, confirm
git statusbefore the next group. - Finish with a clean working tree (scoped run: every listed file committed). Unsure how to group a file → ask.