Committing staged with message

Skill qte77/claude-code-plugins/.claude/skills/committing-staged-with-message

Generate commit message for staged changes, pause for approval, then commit. Stage files first with `git add`, then run this skill.From its SKILL.md

Install

npx -y skills add qte77/claude-code-plugins --skill committing-staged-with-message

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

reads credentialsReads from 1 credential source: `.gitmessage`.
2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
runs commandsInstructs the agent to run 6 commands, including `git diff --staged --name-only` and 5 more.

SKILL.md

1.8 KB, 381 tokens by cl100k_base, as published. Nobody here has run it

Commit staged with Generated Message

Step 1: Analyze Staged Changes

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.

Step 2: Generate Commit 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.

Step 3: Pause for Approval

Please review the commit message.

Approve: "yes", "y", "commit", "go ahead"
Edit: Provide your preferred message
Cancel: "no", "cancel", "stop"

Step 4: Commit

Once approved:

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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most pr commit review skills give in 381 tokens

Counted across 1,055 of the 1,911 authors here whose files we hold, read 2026-09-06

Use conventional commit message formatin 150 of 1055, across 145 files
Announce skill usage at startin 78 of 1055
Use imperative mood for commit descriptionsin 54 of 1055, across 51 files
Add directory to gitignore if not ignoredin 52 of 1055, across 41 files
Use imperative mood for commit subjectin 52 of 1055
Run tests to verify clean baselinein 42 of 1055, across 32 files
Push branch to originin 40 of 1055, across 38 files
Verify worktree directory is ignored before creationin 39 of 1055, across 32 files
Delete branches after mergingin 38 of 1055, across 30 files
Create worktree with new branchin 37 of 1055, across 32 files
Wrap body text at 72 charactersin 36 of 1055, across 34 files
Auto-detect and run project setupin 35 of 1055, across 27 files

Said here and by no other author read

List staged files
Include diff stats in body
Pause for user approval
Verify commit success

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.