Our review
Generates a commit message from staged changes, pauses for approval, then commits with a GPG signature.
Strengths
- Automatically analyzes changes for a precise, structured commit message
- Detects added/removed symbols and diff statistics
- Allows user to approve, edit, or cancel before committing
Limitations
- Requires files to be staged with git add first
- May be slow with many files (over 10)
- Depends on Bash and Git being available in the environment
Use this skill when you have staged changes and want a consistent, well-formatted commit message following project conventions.
Do not use it for unstaged changes or when you prefer to write the commit message manually without assistance.
Security analysis
SafeThe skill uses only local git commands and does not perform destructive, exfiltrating, or obfuscated actions. All operations require explicit user approval before committing, and no external data is transmitted.
No concerns found
Examples
Commit my staged changes with a generated commit message.Generate a commit message for the staged changes and commit them after I review it.Run the commit skill to analyze my staged files and create a signed commit.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
Step 1: Analyze Staged Changes
Run these commands using the Bash tool to gather context:
git diff --staged --name-only- List staged filesgit diff --staged --stat- Diff stats summarygit log --oneline -5- Recent commit stylegit diff --staged- Review detailed staged changes. Size guard: if--statshows >10 files or >500 lines changed, skip the full diff and rely on--stat+--name-onlyto 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
--statsummary line) — MUST be the last line of the body- Format:
+ symbol_name,- symbol_name - Omit for config/docs/formatting-only changes
- Format:
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
Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.