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

  1. Review full diff and status; read recent log for style.
  2. Identify logical groups: feature/fix, its tests, config, formatting-only, docs, assets.
  3. Per group: stage those files explicitly by name, commit with a HEREDOC message, confirm git status before the next group.
  4. Finish with a clean working tree (scoped run: every listed file committed). Unsure how to group a file → ask.

Grouping rules

Installs
59
GitHub Stars
19
First Seen
Feb 13, 2026