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, and misconfigured bindings that cause runtime failures or security issues. ## Core Features & Use Cases - Best-Practice Code Review: Checks Workers code against canonical rules covering streaming, waitUntil, bindings, observability, security, and type safety, with severity-ranked findings. - Config Validation: Verifies wrangler.jsonc fields including compatibility_date, nodejs_compat, observability, secrets handling, and binding-code consistency against the official wrangler schema. - Retrieval-First Workflow: Fetches the latest Cloudflare docs, @cloudflare/workers-types, and wrangler config schema before reviewing, avoiding outdated API assumptions. - 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 nodejs_compat flag, and a public-HTTP Worker-to-Worker call that should be a service binding. ## Quick Start Review my Cloudflare Worker code and wrangler.jsonc against the latest Workers best practices and flag any anti-patterns.