wrangler

What problem does it solve? Cloudflare Wrangler CLI flags and configuration fields change frequently, so relying on memorized commands leads to broken deployments, misconfigured bindings, and lost secrets. This Skill ensures every Wrangler command and config edit is grounded in the project's installed version and current official documentation. ## Core Features & Use Cases - Project Inspection: Detects the package manager, installed Wrangler version, framework, and active config file before running any command, so changes target the right Worker, environment, and account. - Documentation-Grounded Commands: Maps each task (deployments, secrets, environments, bindings, rollbacks, local development) to the correct Cloudflare docs page or local wrangler --help output instead of guessing syntax. - Safe Change Application: Enforces best practices such as keeping secrets out of logs, checking environment inheritance, reconciling dashboard changes, and validating with wrangler deploy --dry-run and regenerated types. - Use Case: You need to add a KV binding to a staging environment on an existing Workers project. The Skill inspects your wrangler.jsonc, verifies environment inheritance, checks the installed schema, applies the binding, regenerates types, and dry-runs the deploy. ## Quick Start Use the wrangler skill to add a KV namespace binding to my staging environment and validate the deployment with a dry run.