Why this matters
Edge misconfigurations can cause global outages (redirect loops) and security regressions.
If a PR changes redirect/header configuration (e.g., middleware redirects, CDN headers, security headers), validate it against the active edge rules to avoid conflicts. - If a Cloudflare MCP is available: fetch active rules and detect potential redirect loops, duplicate rules, or header conflicts. - Otherwise: require the author to link the relevant Cloudflare rules/screenshots in the PR description.
Edge misconfigurations can cause global outages (redirect loops) and security regressions.
Side-by-side examples engineers can pattern-match during review.
Adds app-level redirect that conflicts with an existing Cloudflare redirect rule.Checks active Cloudflare rules, avoids loops, and documents the intended precedence.redirect change; no edge-rule validationCloudflare rule check + no loop + precedence documentedFrom the same buckets as this rule.