conventional-commits
Conventional Commits Skill
Generate well-formatted conventional commit messages from staged changes.
Instructions
When asked to commit changes or when the user runs /commit:
- Analyze staged changes using
git diff --staged - Identify the type of change:
feat: New featurefix: Bug fixdocs: Documentation onlystyle: Formatting, no code changerefactor: Code restructuringtest: Adding/updating testschore: Maintenance tasks
- Determine the scope (optional): The part of codebase affected
- Write the message following this format:
<type>(<scope>): <short description> <body - what and why, not how> <footer - breaking changes, issue refs>
Examples
Simple feature:
feat(auth): add password reset functionality
Bug fix with body:
fix(api): handle null response from external service
The weather API occasionally returns null during maintenance windows.
Added defensive check to prevent crash and return cached data instead.
Breaking change:
feat(db)!: migrate from MySQL to PostgreSQL
BREAKING CHANGE: Database connection strings must be updated.
See migration guide in docs/migration-v2.md
Rules
- Keep the first line under 72 characters
- Use imperative mood ("add" not "added")
- Don't end with a period
- Reference issues when applicable
- Add
!after type for breaking changes
More from claude-code-community-ireland/claude-code-resources
security-review
Security review checklist covering OWASP Top 10, authentication, authorization, input validation, secrets management, and common vulnerability patterns. Reference when reviewing code for security.
7design-patterns
Reference library of proven UI design patterns, component templates, and sector-specific conventions for high-quality design generation.
6pr-description
Pull request authoring standards — structured descriptions, linking issues, providing test evidence, and writing good summaries. Reference when creating or describing pull requests.
4refactoring-patterns
Safe refactoring techniques — extract method, rename, move, inline, and structural patterns. Includes code smell identification and transformation recipes. Use when refactoring code or improving structure.
4skill development
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
4community-code-reviewer
Perform thorough, constructive code reviews on pull requests and code changes. Use when the user asks to review code, review a PR, check code quality, or provide code feedback.
4