commit-lint
Validate commit messages against conventional commit format
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
/commit-lint — Commit message validation
Ensure commits follow conventional commit format and pass quality checks.
Commit Format
<type>[scope]: <description>
[body]
[footer]
Commit Types
| Type | Purpose |
|---|---|
feat |
New feature |
fix |
Bug fix |
docs |
Documentation |
style |
Formatting (no code change) |
refactor |
Code restructuring |
test |
Adding/fixing tests |
chore |
Build/tooling changes |
perf |
Performance improvement |
ci |
CI configuration |
build |
Build system changes |
revert |
Revert previous commit |
Pre-commit Checks
Auto-detected based on lock files (bun/pnpm/yarn/npm):
$PM run format # Biome formatting
$PM run lint # Linting checks
$PM run check # Quality verification
Hook Detection
| File | System |
|---|---|
lefthook.yml |
lefthook (automatic) |
.pre-commit-config.yaml |
pre-commit (automatic) |
| Neither | Manual validation |
Examples
feat: add user authentication
fix(auth): resolve login validation error
docs: update API documentation
feat!: change API interface
BREAKING CHANGE: Method now requires email parameter
Guidelines
- Keep header under 72 characters
- Use present tense: "Add" not "Added"
- Solo-authored commits only (no co-authorship)
- AI attribution goes in PR description, not commits
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-01-26
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!