Why this matters
Keeps releases consistent and reduces process gaps that lead to production issues.
If the repo defines a Definition of Done (e.g., `DOD.md`, `CONTRIBUTING.md`), ensure the PR meets it. To enable this check, reference the file path in the PR or ask to review it explicitly. Confirm bureaucratic requirements (docs, tests, design approval, rollout plan) are satisfied or explicitly marked as not applicable.
Keeps releases consistent and reduces process gaps that lead to production issues.
Side-by-side examples engineers can pattern-match during review.
Skips required docs/tests per DoD with no acknowledgment.PR checklist explicitly maps DoD items to evidence (tests, docs, approvals).DoD exists but PR provides no evidenceDoD checklist + links to tests/docs/approvalsFrom the same buckets as this rule.
If the PR claims to fix a specific issue (e.g., 'Fixes #123' / 'Fix PAY-123'), validate it against the real production error. - If an observability MCP is available (Sentry/Datadog/Bugsnag): fetch the event/stack trace and confirm the change addresses the root cause. - Require a regression test (or a clearly documented reason why a test cannot be added). Call out fixes that only hide symptoms (catch-and-ignore, broader retries, defaulting values) without removing the underlying failure mode.