01
What this skill does
Use this skill when the staged changes are ready but the commit wording needs to be precise. It inspects staged status, staged stats, and the staged diff, then infers the correct Conventional Commit type and message without mutating the repository.
02
When to use it
- 01Generating a clean subject and body from the current staged batch.
- 02Checking whether staged work is too mixed for one honest commit.
- 03Keeping commit wording grounded in what will actually be committed.
03
How it works
- 01
Check `git status --short`, `git diff --cached --stat`, and `git diff --cached`.
- 02
Stop if nothing is staged rather than falling back to unstaged work.
- 03
Infer the commit type from the staged behavior, not from branch names or intent alone.
- 04
Draft a Conventional Commit subject and body that names the actual user-visible or structural change.
- 05
Return the message text without running `git commit`.
04
What you get back
- 01A Conventional Commit message proposal.
- 02A warning when the staged batch is mixed or misleading.
- 03No repository mutations.
05
Important boundaries
- 01Inspect staged changes only.
- 02Do not stage files, read unstaged diffs, or create the commit.
- 03Do not invent product context that is not visible in the staged diff.
06