Our review

Generates a commit message for staged changes, pauses for approval, then commits with GPG signing.

When to use it

Use this skill when you have staged changes ready to commit and want a consistent commit message following project conventions.

When not to use it

Avoid this skill for very frequent commits or when you prefer writing each message manually without an approval step.

name: committing-staged-with-message description: Generate commit message for staged changes, pause for approval, then commit. Stage files first with `git add`, then run this skill. compatibility: Designed for Claude Code metadata: model: haiku argument-hint: (no arguments needed) disable-model-invocation: true allowed-tools: Bash, Read, Glob, Grep

Commit staged with Generated Message

Run these commands using the Bash tool to gather context:

git diff --staged --name-only - List staged files
git diff --staged --stat - Diff stats summary
git log --oneline -5 - Recent commit style
git diff --staged - Review detailed staged changes. Size guard: if --stat shows >10 files or >500 lines changed, skip the full diff and rely on --stat + --name-only to generate the message.

Use the Read tool to check .gitmessage for commit message format and syntax.

The commit message body MUST include (concisely — no padding, no redundancy):

What changed: bullet points per file or logical group
Symbols added/removed (when applicable): functions, classes, tests
Diff stats: lines added/removed (from --stat summary line) — MUST be the last line of the body
- Format: + symbol_name, - symbol_name
- Omit for config/docs/formatting-only changes

Keep the message laser-focused. Do not repeat the subject line in the body.

Please review the commit message.

Once approved:

git commit --gpg-sign -m "[message]" - Commit staged changes with approved message (GPG signature mandatory)
git status - Verify success