conventional-commit
Formats and validates Git commit messages according to the Conventional Commits standard.
Install
mkdir -p .claude/skills/conventional-commit && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/1393" && unzip -o skill.zip -d .claude/skills/conventional-commit && rm skill.zipInstalls to .claude/skills/conventional-commit
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Formats Git commit messages using the Conventional Commits standard and enforces project-specific linting rules.Key capabilities
- →Format commit headers using Conventional Commits standard
- →Validate commit message structure against linting rules
- →Enforce maximum header length of 100 characters
- →Ensure subject lines lack trailing punctuation
- →Apply imperative present tense to commit descriptions
How it works
The skill analyzes staged changes to generate or validate commit messages based on predefined types and strict formatting rules.
Inputs & outputs
When to use conventional-commit
- →Generate commit message from changes
- →Validate conventional commit structure
- →Standardize git commit headers
About this skill
Conventional Commit Skill
Use this skill to generate or validate Git commit messages.
Instructions
- Analyze Changes: Look at the staged changes (using
git diff --cached) or provided content. - Determine Type: Choose the most appropriate type from:
feat: A new featurefix: A bug fixchore: Maintenance or tool changes (Husky, EditorConfig, etc.)docs: Documentation only changesstyle: Changes that do not affect the meaning of the code (white-space, formatting, etc.)refactor: A code change that neither fixes a bug nor adds a featureperf: A code change that improves performancetest: Adding missing tests or correcting existing tests
- Format Header:
- Format:
<type>[optional scope]: <description> - CRITICAL: The header must NOT exceed 100 characters.
- CRITICAL: The description must NOT end with a period/full stop.
- Use imperative, present tense: "change", not "changed" or "changes".
- Use lowercase for the starting character of the description.
- Format:
- Body (Optional): Provide additional context if the change is complex. Wrap lines at 72 characters.
- Footer (Optional): Mention breaking changes or reference issues (e.g.,
Resolves #123).
Project Specifics
- This project uses
@commitlint/config-conventional. - Maximum header length: 100 characters.
- No trailing punctuation in the subject line.
When not to use it
- →When writing commit messages that do not follow conventional standards
- →When the commit message exceeds 100 characters
Prerequisites
Limitations
- →Subject line must not end with a period
- →Strict 100-character limit for headers
How it compares
It enforces a standardized, machine-readable commit format that improves project history clarity compared to free-form messages.
Compared to similar skills
conventional-commit side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| conventional-commit (this skill) | 3 | 6mo | No flags | Beginner |
| resolve-conflicts | 81 | 8mo | Review | Intermediate |
| dependency-upgrade | 26 | 5mo | Review | Intermediate |
| git-commits | 21 | 4mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
resolve-conflicts
antinomyhq
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
git-commits
bonny
Create well-structured git commits in logical chunks following best practices
git-advanced-workflows
wshobson
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
github-multi-repo
ruvnet
Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration
git-workflow-enforcer
CrazyDubya
Ensures commits follow conventional commits, branch naming conventions, and PR templates. Use when creating commits, branches, or PRs, or when user mentions git workflow.