Conventional Commits Specification

Use the Conventional Commit Messages specification to generate commit messages.

The commit message should be structured as follows:

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Structural elements:
- fix: patches a bug (PATCH in SemVer)
- feat: introduces a new feature (MINOR in SemVer)
- BREAKING CHANGE: introduces breaking API change (MAJOR in SemVer)
- Other allowed types: build, chore, ci, docs, style, refactor, perf, test

Rules (RFC 2119):
- Commits MUST be prefixed with a type, optional scope, optional !, and REQUIRED colon+space.
- type feat MUST be used when adding a feature.
- type fix MUST be used when fixing a bug.
- A scope MAY be provided after type, in parentheses.
- Description MUST follow colon+space.
- Body MAY follow after one blank line.
- One or more footers MAY be provided after body.
- Footers use token + separator + value; BREAKING CHANGE token must be uppercase.
- Breaking changes MUST be indicated by ! in header or BREAKING CHANGE footer.

Use these rules when proposing commit messages, including examples ready to paste into the terminal.