commit
Installation
SKILL.md
Commit only the user's staged changes. Do not stage or repartition files, manage branches, resolve conflicts, create merge commits, amend history, push, or interact with remotes.
Prepare and confirm
- Check
git statusand readgit diff --cached, not just filenames or stats. Stop for an in-progress merge or unresolved conflicts. If nothing is staged, report modified/untracked files and ask the user to stage their selection or authorize a separate staging task; recheck the index afterward. - Read references/format.md to choose type and one emoji. Classify by primary semantic intent, not line count or generated-file volume. Inspect large diffs in coherent file/package groups; ask about intent only if material ambiguity remains. For independent changes, propose a split for the user to arrange rather than altering the index.
- Draft the message using the rules below, display it in a code block, and ask “Commit with this message?” Wait for approval clearly referring to this message and the reviewed staged changes; a brief affirmation can suffice.