Committing staged with message

A Claude Code plugin marketplace providing skills, rules, and scripts extracted from a production development workflow.

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.

One thing to look at

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.

Copied from the file, not written here

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

1.8 KB, as published. Nobody here has run it

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