type (required): Primary intent of the change. feat and fix map to semantic versioning. Additional allowed types include: docs, style, refactor, perf, test, build, ci, chore, revert.
scope (optional): Short component or package name in parentheses, e.g., feat(parser): ....
! (optional): Indicates a breaking change and can appear after type or scope.
description (required): Short, imperative summary in lower case (no trailing period). Aim for ≤ 72 characters.
body (optional): Explain what/why; wrap at ~72 characters.
footers (optional): Git trailer format, e.g., BREAKING CHANGE: ..., Refs: #123, Closes: #123.

Workflow

Review changes and identify the primary intent (feature, fix, docs, etc.).
Choose the type and optional scope. If changes span multiple intents, prefer separate commits; otherwise pick the highest-impact type.
Determine whether the change is breaking. If yes, add ! and/or a BREAKING CHANGE: footer.
Write a concise description in imperative mood.
Add body and footers as needed for context, rationale, or issue links.
Validate against the checklist below.

Checklist

Breaking change:

feat(api)!: drop deprecated v1 endpoints

BREAKING CHANGE: v1 endpoints were removed. Use /v2 instead.

Revert:

revert: feat(auth): add refresh token rotation

This reverts commit 1234abcd.