Conventional Commits — Team Guidelines with Lots of Examples
The format (one line) type(scope)!: subject type : one of feat , fix , perf , refactor , chore , docs , test , build , ci , style , revert scope (optional) : focus area like frontend , backend , api , db , billing , search , auth , infra ! : indicates a breaking change ( also add a BREAKING CHANGE: footer in the body) Rules we enforce (team policy) Header Max 100 characters No trailing period Body (optional but recommended) Leave one blank line between header and body Explain what and why ; wrap lines around ~72–100 chars Breaking changes Either: feat(scope)!: ... Or add a footer line: BREAKING CHANGE: describe impact and migration SemVer mapping (cheat-sheet) fix: → PATCH feat: → MINOR BREAKING CHANGE or ! → MAJOR Copy-paste templates ...