conventional-commits

| feat | New feature | MINOR | | fix | Bug fix | PATCH | | docs | Documentation only | none | | style | Formatting, whitespace (no logic change) | none | | refactor | Code restructure (not a fix or feature) | none | | perf | Performance improvement | none | | test | Adding or fixing tests | none | | build | Build system, dependencies (npm, gradle…) | none |

| ci | CI configuration (GitHub Actions, CircleCI…) | none | | chore | Maintenance not fitting above types | none | | revert | Reverts a previous commit | none |

Two ways to signal a breaking change (can combine both):

Write, review, and validate commit messages following the Conventional Commits v1.0.0 specification. Use when: (1) crafting a git commit message for any change, (2) reviewing or correcting an existing commit message, (3) choosing the right commit type for a change, (4) deciding how to mark a breaking change, (5) writing multi-line commits with body and footers, or (6) understanding how commits map to SemVer bumps (PATCH/MINOR/MAJOR). Covers all standard types: feat, fix, docs, chore, refactor, perf, test, build, ci, style, revert. Source: jgamaraalv/ts-dev-kit.