Commit and pull request hygiene
Rules on the change itself rather than the code: commit message format, PR description, size limits, required labels or linked tickets.
Sub-techniques
2
| ID | Name | Description |
|---|---|---|
V1004.001 | Commit message lint | Enforce a message convention so changelogs and release tooling can parse history. |
V1004.002 | Pull request rules | Fail or warn when a PR is too large, lacks a description, or touches files without matching tests or docs. |
Craft it
- Write the rules you already enforce by hand in review as a Dangerfile or commitlint config.
- Start as warnings, then turn the rules people respect into failures.
- Keep size thresholds per directory, not global.
Reverse engineer it
Signs that a codebase already runs this technique, and where to read how it is configured.
- commitlint.config.js, a Dangerfile, or a PR title check in CI.
- Release tooling that parses conventional commits (release-please, semantic-release).
Open-source packages
2
- commitlint conventional-changelog/commitlint
- Danger JS danger/danger-js