Raw view: Conventional Commits

---
description: Write commit messages in Conventional Commits format.
alwaysApply: true
---

# Conventional Commits

Every commit an agent makes on this repo must be a Conventional Commit. Humans
skim `git log`; tools parse it. Do not invent a parallel style.

## Format

```
type(scope): subject

optional body

optional footer
```

- **type** (required): feat, fix, docs, style, refactor, perf, test, build, ci, chore.
- **scope** (optional): a short area name already used in the repo (`auth`, `worker`, `scan`).
- **subject**: imperative, lowercase, no trailing period, ≤72 characters.
  Good: `feat(auth): add Google sign-in`. Bad: `Added Google login.`

## Body

Explain *why*, not what the diff already shows. Wrap at 100 characters. If the
change is a breaking API, start the body with `BREAKING CHANGE:` and a
migration hint.

## Do not

- Mix unrelated work in one commit.
- Mention ticket numbers in the subject (footers are fine: `Fixes #123`).
- Use `update` or `misc` as a type.