What problem does it solve? Cloudflare Workers APIs, types, and wrangler configuration change frequently, so code written from stale knowledge often contains anti-patterns like floating promises, global request state, hardcoded secrets, or incorrect binding access that cause runtime failures and security issues. ## Core Features & Use Cases - Best-Practice Rule Enforcement: Applies canonical rules for streaming, waitUntil, bindings, observability, Web Crypto, and error handling, with correct patterns and anti-patterns for each. - Type and Config Validation: Checks Env interfaces, handler signatures, binding-code consistency, compatibility_date, nodejs_compat, and secrets handling against the latest workers-types and wrangler config schema. - Structured Code Review Workflow: Runs an 8-step review process with severity-rated findings (CRITICAL/HIGH/MEDIUM/LOW) including file, line, evidence, and suggested fixes. - Use Case: Before deploying a new Worker that reads from R2 and calls another Worker, run a review to catch a hand-written Env interface, a missing service binding, and an unawaited fetch that would silently drop webhook deliveries. ## Quick Start Review my Cloudflare Worker code and wrangler.jsonc for best-practice violations and anti-patterns before I deploy.