Why this matters
Avoids piling changes onto an unstable system and reduces MTTR during incident response.
Before approving/merging risky changes, check whether there is an active critical production incident. - If an incident/monitoring MCP is available (PagerDuty, Datadog Monitors): query for active Sev1/Sev2 incidents. - If there is an active incident: warn the author and suggest delaying merges/deploys or using an explicit emergency override process.
Avoids piling changes onto an unstable system and reduces MTTR during incident response.
Side-by-side examples engineers can pattern-match during review.
Merges a risky deploy while an ongoing Sev1 incident is open.Flags active incident and recommends deploy freeze until resolved.Active incident exists; PR proceeds with no warningActive incident warning + freeze/override guidanceFrom 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.