Committing staged with message
Skill qte77/claude-code-plugins/plugins/commit-helper/skills/committing-staged-with-message
A Claude Code plugin marketplace providing skills, rules, and scripts extracted from a production development workflow.
npx -y skills add qte77/claude-code-plugins --skill committing-staged-with-messageAssembled 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.
What its author says it does
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.
SKILL.md
1.5 KB, as published. Nobody here has run it
Commit Staged with Generated Message
Step 1: Analyze Staged Changes
Run using the Bash tool:
git diff --staged --name-only— list staged filesgit diff --staged --stat— diff stats summarygit log --oneline -5— recent commit style
Size guard: If --stat shows >10 files or >500 lines changed, skip full
diff and rely on --stat + --name-only. Otherwise also run git diff --staged
for detailed review.
Step 2: Generate Commit Message
Read .gitmessage for format (conventional commits: type[(scope)][!]: description).
Body guidelines (keep concise — no padding):
- What changed: bullet points per logical group
- For large changes, include diff stats summary as last line
Keep the message laser-focused. Don't repeat the subject line in the body. Small changes (1-2 files, <50 lines) need only a subject line, no 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]"— GPG signature mandatorygit status— verify success