Use when creating git commits, staging changes, or writing commit messages. Provides Angular conventional commit format guidelines, atomic commit principles, and strategies for splitting multi-concern changes into logical commits.
Commits follow the Angular conventional commit format: <type>(<scope>): <description>. Each commit should be atomic (single purpose) and use imperative mood ("add feature" not "added feature").
| Type | Purpose |
|---|---|
feat | New feature |
fix | Bug fix |
docs | Documentation only |
style | Formatting, whitespace (not CSS) |
refactor | Code change without feature/fix |
perf | Performance improvement |
test | Adding or fixing tests |
build | Build system or dependencies |
ci | CI configuration |
chore | Other (no src/test changes) |
revert | Reverts previous commit |
<type>(<scope>): <description>
[optional body]
[optional footer]
Split when changes involve:
Good commit messages:
feat: add user authentication systemfix: resolve memory leak in rendering processdocs: update API documentation with new endpointsrefactor: simplify error handling logic in parserfeat(auth): implement transaction validationfix!: patch critical security vulnerability in auth flowSplit commit sequence:
feat(types): add new solc version type definitionsdocs: update documentation for new solc versionsbuild: update package.json dependenciestest: add unit tests for new solc version features