Our review
Generates commit messages using the Conventional Commits format and creates commits from staged changes.
Strengths
- Structures messages clearly with type and optional scope
- Automates adherence to commit best practices
- Analyzes staged changes to determine the appropriate type
Limitations
- Requires changes to be staged first
- May not accurately capture the intent behind complex changes
- Only adds a body when needed, potentially omitting important context
Use this skill to standardize commit messages in a project following Conventional Commits.
Avoid it if you prefer manually writing highly detailed messages or if your project uses a different commit format.
Security analysis
SafeThe skill only instructs to run 'git diff --staged' to read staged changes, which is a safe, read-only operation. No destructive, exfiltrating, or obfuscated commands are used.
No concerns found
Examples
Write a commit message for the staged changes using Conventional Commits format.Create a commit with type 'feat' and scope 'auth' for the staged changes.Review the staged changes and suggest an appropriate Conventional Commit message.name: commit description: Generates commit messages and creates commits. Use when writing commit messages, committing changes, or reviewing staged changes.
Commit Messages
Use Conventional Commits format.
Format
<type>(<scope>): <description>
[optional body]
Types
feat: User-facing features or behavior changes (must change production code)fix: Bug fixes (must change production code)docs: Documentation onlystyle: Code style/formatting (no logic changes)refactor: Code restructuring without behavior changetest: Adding or updating testschore: CI/CD, tooling, dependency bumps, configs (no production code)
Scopes
Optional. Use when it adds clarity. Examples: ui, api, state, auth.
Examples
feat(search): add infinite scroll to results
fix(album): correct image path validation
refactor(state): simplify album loading machine
chore: add husky pre-commit hooks
docs: update API documentation
test: add E2E tests for login flow
Instructions
- Run
git diff --stagedto see staged changes - Analyze the changes and determine the appropriate type
- Write a concise description (under 72 characters)
- Add body only if the "why" isn't obvious from the description
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.