Commit conventions

Leadline repositories follow Conventional Commits: a lightweight convention for commit messages. Each subject line encodes the kind of change (feat, fix, chore, and others) and a short summary, optionally with scope in parentheses. That keeps git log scannable, helps reviewers infer risk, and lets tooling generate changelogs or enforce policies.

Use the form type(scope): summary when scope adds clarity (for example which package or area changed). A longer body is fine when you need to explain why or document breaking changes using the spec’s BREAKING CHANGE rules.

For the full specification, allowed types, footers, and breaking-change notation, see the official documentation: conventionalcommits.org.