Why this matters
Prevents repeat incidents by ensuring the PR targets the actual failing path in production.
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.
Prevents repeat incidents by ensuring the PR targets the actual failing path in production.
Side-by-side examples engineers can pattern-match during review.
Fixes #123: wrap everything in try/catch and return 200.Fixes #123: reproduce failing stack trace, fix null invariant, add regression test, and keep error reporting intact.catch(Exception) { return OK; } // hides production errorFix root cause + regression test + Sentry event linkFrom the same buckets as this rule.