Quick Reference

format: `<type>(<scope>): <description>`

`api:` API endpoint changes
`feat:` New features
`fix:` Bug fixes
`refactor:` Code restructuring
`perf:` Performance improvements
`style:` Formatting and styling
`test:` Test additions or changes
`docs:` Documentation updates
`ui:` Interface changes
`build:` Build system changes
`dependencies:` Package updates
`ops:` Infrastructure changes
`chore:` Maintenance tasks

tips:

- Use imperative: "add/fix" not "added/fixed"
- Keep first line < 72 chars
- Add scope when possible: `feat(auth):`
- Reference issues: "fixes #123"

Commit Type Format

<type>(<optional scope>): <description>

Example: feat(auth): add OAuth2 authentication

Commit Types

api

Use for changes that affect API endpoints or interfaces

• Good: api(users): add pagination to users endpoint
• Bad: api: made some API changes
• When to use: New endpoints, changes to request/response structures, API versioning

feat

Use for new features and major functional additions

• Good: feat(search): implement fuzzy search algorithm
• Bad: feat: new stuff
• When to use: New user-facing features, significant new functionality

fix