land-and-deploy

To merge a PR, wait for CI, and deploy to production in one step, you need an automated release coordination workflow. This Skill orchestrates the entire process by enforcing pre-merge checks, monitoring CI status, and executing safe production deployments with health validation.

A canary deployment validates production health by routing a subset of traffic to the new release and checking health endpoints. This Skill uses rollback canaries to automatically detect failures during production rollout and revert changes if health checks do not pass.

To automatically deploy the current branch to production after PR merge, the workflow auto-detects the PR from your current branch. It enforces merge permissions and pre-merge checks before proceeding to the production deployment phase.

Yes, you can deploy a specific PR number to production. When the current branch is not sufficient, the workflow accepts a PR number or URL for verification, ensuring the correct pull request is merged and deployed safely.

If production health checks fail during a canary rollout, the deployment is automatically rolled back. The workflow coordinates safe end-to-end releases by validating health via canary checks and executing rollback options on failure to prevent bad production states.

Yes, this release management workflow enforces CI status before merging. It coordinates safe end-to-end releases by waiting for CI to complete, verifying pre-merge checks, and confirming merge permissions before allowing a pull request to merge and deploy.