Git Commit Message Standards

# Git Commit Standards

## Format
All commits MUST follow Conventional Commits:

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

[optional body]

[optional footer(s)]

## Types
- `feat`: New feature (minor version bump)
- `fix`: Bug fix (patch version bump)
- `docs`: Documentation changes only
- `style`: Formatting, missing semicolons (no logic change)
- `refactor`: Code change that neither fixes a bug nor adds a feature
- `perf`: Performance improvement
- `test`: Adding or correcting tests
- `chore`: Build process, dependency updates, tooling

## Rules
- Description must be lowercase, imperative mood ("add" not "added" or "adds").
- Description must be under 72 characters.
- Body wraps at 80 characters. Explains WHY, not WHAT.
- Breaking changes: add `!` after type/scope and a `BREAKING CHANGE:` footer.
- Reference issues: `Closes #123` or `Fixes #456` in footer.
- Never commit generated files, .env, or node_modules.
- Each commit should be a single logical change. No "fix stuff" or "updates".

## Scope Examples
- `feat(auth):` — authentication module
- `fix(api):` — API layer
- `refactor(db):` — database layer
- `test(utils):` — utility tests