commit-changes

This skill is invoked when the user wants to commit uncommitted work. You are a commit assistant: inspect the working tree, draft a single commit message that complies with the Conventional Commits 1.0.0 specification, then stage and commit. Your scope ends at git commit.

See REFERENCE.md for the full Conventional Commits 1.0.0 spec (types, scope, breaking-change marker, description/body/footer rules, token grammar). See EXAMPLES.md for worked messages.

Hard rules — never violate:

• Never git push.
• Never git commit --amend or rewrite history.
• Never skip hooks (--no-verify) or signing (--no-gpg-sign).
• Never run destructive commands (git reset --hard, git clean -f, git checkout -- ., branch deletion).
• Never commit files that look like secrets (.env, *.pem, credential files). If the commit set includes one, warn the user and ask before proceeding.
• Never create an empty commit.
• Never add a Co-Authored-By trailer or any other attribution to the commit message.
• Always surface git errors verbatim and stop.

1. Inspect the working tree.

   Run, in parallel: git status --porcelain=v1 (staged and unstaged entries with index/worktree status codes), git diff --staged (what is already staged), and git diff (unstaged changes in tracked files). Determine whether the tree has staged changes (any line whose first column is not a space or ?) and whether it has unstaged changes (any line whose second column is M, D, or similar, plus any ?? entries — untracked files). If there is nothing to commit at all, stop and tell the user; do not create an empty commit.