git-commit

Run git commit without staging anything new; only the contents already in the index are recorded. This skill inspects git diff --cached first and commits exactly the staged set, never auto-adding unstaged changes.

Group changes by kind (feature, fix, refactor, docs) and by scope or module, then stage and commit each unit separately in dependency order. This skill automates that split by reading the full diff and untracked files before planning the commit sequence.

Conventional Commits uses the pattern type(scope): message, where type is one of feat, fix, refactor, test, style, chore, docs, ci, or perf. The subject stays lowercase, imperative, around 50 characters, with an optional body explaining motivation.

No. The skill never runs any git push variant, even when asked to commit and push. After committing, it asks the user to confirm the push as a separate, explicit action.

The underlying problem is fixed and a new commit is created rather than using --amend, since the failed hook run produced no commit. Hooks are never bypassed with --no-verify or --no-gpg-sign.

git add -A and git add . can unintentionally include secrets, credential files, or large binaries. Staging files explicitly by name prevents accidental inclusion, and detected secrets trigger a warning instead of a commit.