qte77/committing-staged-with-message
plugins/commit-helper/skills/committing-staged-with-message/SKILL.md
Generate commit message for staged changes, pause for approval, then commit. Stage files first with `git add`, then run this skill.
$ install --global
skillsauthnpx skillsauth add qte77/claude-code-plugins committing-staged-with-messageInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 18, 2026, 2:48 AM32.3s2 files scanned
SKILL.md
- 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
- model:
- haiku
- argument-hint:
- (no arguments needed)
- disable-model-invocation:
- true
- allowed-tools:
- Bash, Read, Glob, Grep
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
Related Skills
qte77/triaging-security-report
development
VerifiedTrustedCommunity
Verify an external or AI-generated security report against the actual codebase before acting on it. Use when handed a scanner PDF, automated teardown, audit report, or bug-bounty submission — classifies every finding CONFIRMED / OVERSTATED / FALSE-POSITIVE / FABRICATED and salvages the real work items.
2SKILL.mdUpdated Jul 6, 2026
qte77/auditing-website-seo-geo
development
VerifiedTrustedCommunity
Audits a site's SEO and AI-search (GEO) readiness — meta tags, Open Graph/Twitter, JSON-LD, robots/llms conventions — and generates fixes. Use when reviewing search visibility, social previews, structured data, or LLM/AI-crawler discoverability.
1SKILL.mdUpdated Jun 14, 2026
qte77/writing-readme
documentation
VerifiedTrustedCommunity
Generate or update README.md files across three scopes — repo (with project-type detection), account (GitHub user profile), and org (organization profile). Use when creating, updating, or aligning a README to org conventions.
1SKILL.mdUpdated Apr 19, 2026
qte77/auditing-readme
development
VerifiedTrustedCommunity
Audit README.md files against best practices for repos, accounts, or orgs. Detects missing sections, stale links, inconsistent formatting, and convention violations. Use when reviewing README quality across one or many repos.
1SKILL.mdUpdated Apr 19, 2026