cloudflare-deployment-preflight

What problem does it solve?

Cloudflare Workers and Pages deployments often fail in production due to uncaught configuration errors, missing bindings or secrets, incorrect account targeting, or unvetted D1 database migrations, which are costly to fix after a global deploy that takes effect in seconds.

Core Features & Use Cases

• End-to-end pre-deploy validation: Covers account/auth confirmation, dry-run builds, binding/resource cross-checks, secrets verification, and D1 migration review to catch all issues before pushing code.
• Staged gradual rollout support: Uses Wrangler's versions workflow to upload code without serving it, split traffic gradually, and enable instant rollbacks to reduce blast radius of bad changes.
• Post-deploy monitoring: Guides use of wrangler tail to watch live logs for errors during rollout before ramping to 100% traffic.
• Use Case: A team deploying a payment-processing Worker can use this skill to confirm all D1 and KV bindings exist, verify payment secrets are set for the production environment, and stage the rollout to 10% of traffic first to catch edge cases before full exposure.

Quick Start

Use the cloudflare-deployment-preflight skill to validate your Cloudflare Worker or Pages deployment configuration, confirm all required bindings and secrets are correctly set, and stage a safe gradual rollout before pushing to production.