What problem does it solve? Shipping a build to production involves many failure points: wrong release strategy, ungated pipelines, misconfigured Kubernetes probes, missing rollback plans, and no post-deploy visibility. This Skill guides the full interval between "the image builds" and "the release is observably healthy" with concrete, opinionated references. ## Core Features & Use Cases - Release strategy selection: Choose rolling, blue-green, or canary deployments with cost and rollback-speed tradeoffs, plus a written rollback checklist. - CI/CD pipeline gates: Gate ordering (lint → typecheck → test → security scan → build → deploy), GitHub branch protection with required status checks, caching keyed on lockfile hashes, and a complete GitHub Actions workflow. - Kubernetes and readiness: Probe configuration (startup/liveness/readiness), resource requests and limits, RBAC defaults, and a production-readiness ship/block verdict with hard caps. - Post-deploy watch and observability: Baseline-delta monitoring, alert tiers, operator dashboards, and structured logging rules. - Use Case: Before launching a new service, ask for a production-readiness verdict — the Skill audits CI, migrations, webhooks, and rollback paths, then returns a score with blockers and missing evidence. ## Quick Start Ask the assistant to audit whether this project is ready to ship to production and to write the rollback plan before deploying.
