commit

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:

1. Git hooks enforce it (commit will be rejected otherwise)
2. 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 - main library code (src/lib.rs)
• builder - Rhusky builder pattern API
• install - hooks installation logic
• git - git operations

Infrastructure scopes

• version - version bumps
• deps - dependency updates
• ci - CI/CD workflows (use with ci: or chore: type)
• config - configuration files
• hooks - git hooks

Documentation scopes

• readme - README.md changes
• claude - CLAUDE.md, Claude Code skills

Testing scopes

• tests - general test changes

Examples

Good commit messages

feat(builder): add custom hooks directory support
fix(install): handle missing git repository gracefully
docs(readme): update installation instructions
refactor(lib): extract git operations into functions
test(builder): add tests for skip_in_env method
chore(deps): update tempfile to 3.24
ci(workflows): add release binary uploads
feat(builder)!: change default hooks directory

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(api)!: remove deprecated endpoint

BREAKING CHANGE: The /v1/status endpoint has been removed.
Use /v2/health instead.

This will appear prominently in the changelog.

Commit Process

1. Stage your changes: git add <files>
2. Commit with message: git commit -m "type(scope): subject"
3. 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(bump): add README badge updates

Updates version badges in README.md when bumping.
Searches for crates.io and docs.rs badge patterns
and replaces version numbers.

Closes #42"

Checking Recent Commits

To see the commit style used in this repo:

git log --oneline -20