# git-commit-conventions

Conventional Commits — subject in imperative mood, body explains the why, breaking changes flagged.

```bash
npx rulepack add git-commit-conventions
```

## What it covers

- The `<type>(<scope>): <subject>` structure with the full type set (`feat`, `fix`, `refactor`, `perf`, `test`, `docs`, `chore`, `ci`, `build`, `revert`)
- Subject style: imperative mood, no trailing period, ≤ 72 chars; body wrapped at 72 explaining the *why*, not the *what*
- `BREAKING CHANGE:` footers (plus issue refs like `Closes #123`) that trigger a major bump in semver tools
- House rules: one logical change per commit, never amend pushed commits on shared branches, split formatter noise from feature commits
- Worked `feat` and `fix` examples showing a well-formed subject, body, and footer

## Source

Rules follow the Conventional Commits specification: https://www.conventionalcommits.org/en/v1.0.0/

## License

MIT