pr-review-checklist

Run the checklist against the PR's changed files and evaluate each of the five gates: correctness, type and build safety, testing, security and privacy, and maintainability. The output is a PASS, CONDITIONAL PASS, or BLOCKED verdict with blockers listed by file.

A solid PR checklist covers correctness of intended behavior, TypeScript compilation and import validity, test coverage for changed logic, auth and input validation on sensitive routes, and adherence to repository naming and structure conventions.

Yes, the type and build safety gate specifically checks that TypeScript compiles for the changed scope, no new diagnostics appear in touched files, and imports and exports remain valid and consistent.

Block a PR when any gate fails critically, such as missing auth or permission checks on sensitive routes, secret or token leakage, broken type safety, or regressions in touched flows. The output lists blockers with file references and remediation steps.

A checklist verifies objective criteria but cannot judge architectural fit, business logic intent, or subtle runtime behavior. It complements rather than replaces human judgment, manual testing, and CI pipeline results.