← ClaudeAtlas

deploy-production-levellisted

Use when the user explicitly asks for a production-grade deployment pipeline, release process, staging to production promotion, per-PR preview environments, or one-click rollback for a web app on GitHub Actions and Cloudflare Workers, or asks to upgrade a repo that already has a deploy.yml / preview.yml / rollback.yml pipeline from an earlier version of this method. Not for projects where a single manual deploy is enough.
tomerhayundev/skills · ★ 0 · DevOps & Infrastructure · score 60
Install: claude install-skill tomerhayundev/skills
# Production-Level Deployment Pipeline Nothing reaches production without passing a quality gate twice, running on staging first, and being promoted by a human. Every production deploy is tagged with its Worker version ID, so rollback is instant and needs no rebuild. AI agents are blocked from deploying by a hook, not just by a rule they are asked to follow. Last verified against the tooling on 2026-09-27. Check the version table before copying anything. ## The pipeline ``` feature/* --PR--> main --PR (promotion)--> production | | every PR: | push to main: | push to production: CI Quality Gate | gate, build, | gate, build, record live version, (required check) | migrate staging D1, | migrate prod D1, deploy, smoke test + Preview URL | deploy --env staging, | (smoke fails: auto-rollback), (optional) | smoke test | tag deploy-<ts>-<sha> with version ID Rollback Production (manual button): wrangler rollback <version ID>. Instant. ``` If any step fails, nothing after it runs. If the production smoke test fails, the job rolls back to the version that was live before it started. ## Current versions (update this table whenever you touch the skill) | Tool | Use | Notes | |---|---|---| | `actions/checkout` | `@v7` | node24 runtime. Actions on Node 20 (`checkout@v4` and friends) lost runner support on 2026-09-23 | | `actions/setup-node` | `@v7` | with