| name | commit |
| description | Create commits following Angular Conventional Commits format with proper scope naming for consistent changelog generation |
Commit Skill
Use this skill when creating git commits. All commits must follow
Angular Conventional Commits format because:
- Git hooks enforce it (commit will be rejected otherwise)
- Cocogitto parses commits to generate release changelogs
Commit Message Format
<type>(<scope>): <subject>
[optional body]
[optional footer]
Requirements:
- Type: lowercase, from allowed list
- Scope: mandatory, lowercase, describes what changed
- Subject: lowercase start, imperative mood, no period
- Breaking changes: add exclamation mark before colon (e.g. feat(api)!:)
Allowed Types
Angular standard types
| Type | Purpose | In Changelog |
|---|
feat | New feature | Yes |
fix | Bug fix | Yes |
docs | Documentation only | Yes |
refactor | Code change (no feat/fix) | Yes |
perf | Performance improvement | Yes |
build | Build system changes | Yes |
style | Formatting, whitespace | No |
test | Adding/fixing tests | No |
ci | CI/CD configuration | No |
Extended types (not in original Angular spec)
These are widely adopted extensions configured in cog.toml:
| Type | Purpose | In Changelog |
|---|
chore | Maintenance, deps, tooling | No |
revert | Revert previous commit | Yes |
Scope Naming Guidelines
Scopes should be consistent to group related changes in changelogs.
Component scopes
lib - library code (src/lib.rs)cli - command-line interfacetoolchain - toolchain detection and management
Infrastructure scopes
version - version bumpsdeps - dependency updatesci - CI/CD workflows (use with ci: or chore: type)config - configuration filesmsrv - minimum supported Rust version
Documentation scopes
readme - README.md changesclaude - CLAUDE.md, Claude Code skills
Testing scopes
tests - general test changes
Examples
Good commit messages
feat(lib): add automatic nightly version detection
fix(toolchain): handle missing rust-toolchain.toml
docs(readme): update installation instructions
refactor(cli): simplify argument parsing
test(lib): add tests for version parsing
chore(deps): update clap to 4.5
ci(workflows): add release binary uploads
feat(cli)!: change default output format
Bad commit messages
feat: add feature # missing scope
Fix(lib): Fix bug # uppercase type and subject
feat(lib): Add feature. # uppercase subject, has period
updated the readme # wrong format entirely
feat(lib) add feature # missing colon
feat(Lib): add feature # uppercase scope
Breaking Changes
For breaking changes, add an exclamation mark after the scope:
feat(cli)!: change default output format
BREAKING CHANGE: Output now uses JSON by default.
Use --text for the old behavior.
This will appear prominently in the changelog.
Commit Process
- Stage your changes:
git add <files>
- Commit with message:
git commit -m "type(scope): subject"
- Hooks automatically run:
- pre-commit: fmt and clippy checks
- commit-msg: validates conventional commit format
- post-commit: verifies signature
If the commit is rejected, fix the issue and try again.
Multi-line Commits
For complex changes, use a body:
git commit -m "feat(lib): add channel override support
Allows specifying a custom nightly channel date.
Useful for pinning to specific nightly versions.
Closes #42"
Checking Recent Commits
To see the commit style used in this repo:
git log --oneline -20
