Our review
Creates Git commits following project conventions, with a strict message format and instructions for a clean history.
Strengths
- Clear and consistent commit messages
- Encourages atomic commits
- Avoids anti-patterns like redundancy or implementation journey
Limitations
- Does not handle merge conflicts
- May miss full context if message is too short
- Relies on existing Git configuration (hooks, conventions)
Use this skill whenever you need to save changes in Git with a well-formatted commit message.
Do not use it when you need a complex commit with many unrelated changes or when you need to modify existing history.
Security analysis
CautionThe skill uses git commands that modify the repository, which is a powerful action. However, it includes safety guidelines to avoid force pushing and amending others' commits, and it does not engage in destructive or exfiltrating behavior. The risk is legitimate for the task.
- •The skill instructs the AI to stage and commit changes to the repository, which could result in unintended commits or loss of work if misused.
Examples
Commit my staged changes with a message following the standard format.Create a commit for all unstaged changes with a descriptive subject line.Commit the current changes with a subject line 'Add user authentication' and a body explaining the new feature.name: commit description: Use when creating a git commit for staged or unstaged changes. Triggers on "commit this", "save my changes", or when implementation work completes and needs version control.
Commit Changes
Create a git commit following project conventions.
Commit Message Format
Subject line: Imperative mood, 50 chars max, capitalized, no period
- "Add spectrum analyzer" NOT "Added spectrum analyzer"
- Test: "If applied, this commit will [your subject]"
Body: Optional. Most commits need only a subject line. When included:
- State WHAT capability exists after this commit (1-2 sentences max)
- Skip if subject line is self-explanatory
Anti-patterns (never include):
- Implementation journey ("was implemented and reverted", "tried X then Y")
- Redundant expansion of subject ("This adds..." when subject says "Add...")
- Phase/step references from planning docs
- Rationale for rejected approaches
Scope: One logical change per commit. Atomic commits simplify review and revert.
Instructions
- Run
git statusandgit diff --staged(orgit diffif nothing staged) to understand changes - Run
git log --oneline -5to see recent commit style - Draft a commit message following the format above
- Stage relevant files and commit:
Simple commit (preferred):
git commit -m "Add vertical offset parameter for linear waveforms"
With body (only when subject needs clarification):
git commit -m "$(cat <<'EOF'
Add vertical offset parameter for linear waveforms
Enables vertical stacking of multiple waveforms in linear mode.
EOF
)"
Safety
- NEVER amend commits you didn't create (check
git log -1 --format='%an %ae') - NEVER force push to main/master
- NEVER skip hooks unless explicitly requested
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.