A precheck is an automated validation that runs before or when a pull request is submitted. It catches routine problems early, keeping review focused on issues that require human judgment. section 4.4.4 section 5.2.2
Use a precheck for issues that are obvious, repeatable, and inexpensive to fix:
- Flag abandoned TODOs, unused variables, commented-out code, debugging statements, and other forgotten code. section 4.4.4
- Run spelling, grammar, lint, style-consistency, language-convention, and in-house-standard checks. section 4.4.4
- Check comments for omissions, inaccuracies, unnecessary content, and copied blocks whose wording was not updated. section 4.4.4
A prepared pull request
A developer opens a pull request containing a console.log(), an abandoned TODO, and a lint violation. The precheck fails, so the pull request is not considered properly prepared until those issues are fixed. section 4.4.4
Choose review tooling that can trigger checks when a pull request opens, connect bots, or run custom tasks and scripts. Automation supports preparation but does not replace decisions about which problems belong in review. section 5.2.2 section 4.4.4
