git-commit

# Git Commit Messages

Create semantic, version-aware commit messages following Conventional Commits 1.0.0 specification.

## Quick Reference

**Format:**
```
<type>[optional scope]: <description>

[optional body]

[optional footer(s)]
```

**Example:**
```
feat(api): add pagination support

Support limit and offset parameters for list endpoints.
Enables clients to fetch large datasets incrementally.

BREAKING CHANGE: Default result limit changed from 100 to 20
```

## Type Selection

| Type | When to Use | SemVer | Example |
|------|-------------|--------|---------|
| `feat` | New feature added | MINOR | `feat(ui): add theme switching` |
| `fix` | Bug patched | PATCH | `fix(auth): correct session validation` |
| `docs` | Documentation only | - | `docs: add API authentication guide` |
| `style` | Code formatting (no logic change) | - | `style: fix indentation in router` |
| `refactor` | Code restructure (no behavior change) | - | `refactor: extract validation logic` |
| `perf` | Performance improvement | PATCH | `perf(api): parallelize database queries` |
| `test` | Adding tests | - | `test: add input validation tests` |
| `build` | Build system changes | - | `build: update build configuration` |
| `ci` | CI configuration | - | `ci: add automated deployment` |
| `chore` | Other changes (tooling, deps) | - | `chore: update dependencies` |
| `revert` | Revert previous commit | - | `revert: feat(api): add endpoint` |

## Common Project Scopes

Choose scopes that match your project architecture. Here are examples across different project types:

### Web Application Projects

| Scope | Component |
|-------|-----------|
| `api` | REST/GraphQL endpoints |
| `frontend` | Client-side UI |
| `backend` | Server-side logic |
| `auth` | Authentication/authorization |
| `database` | Database schemas/migrations |
| `ui` | User interface components |
| `routing` | Application routing |

### CLI/Library Projects

| Scope | Component |
|-------|-----------|
| `cli` | Command-line int