land-and-deploy

Automating a PR merge and deploy to production with health checks requires orchestrating merge, CI wait, deployment, and canary validation. This Skill executes that end-to-end workflow from a merge-ready PR to verified production health.

A canary deployment check validates production health by routing a subset of traffic to the new release and monitoring metrics before full rollout. It is needed in CI-CD workflows requiring automated post-deploy verification before finalizing a release.

Waiting for CI to pass before merging a pull request is handled by monitoring pipeline status and verifying merge readiness. This Skill automates the CI wait phase, ensuring pre-merge checks complete successfully before triggering production deployment.

Yes, the automated deployment workflow supports pre-merge checks, CI wait, canary verification, and selective telemetry or config steps. It applies operational instructions and frontmatter requirements to validate the full promotion flow from PR to production.

The best way to verify production health after an automated PR deploy is running canary checks and post-deploy validation. This Skill automates that verification, ensuring production stability is confirmed before finalizing the release.

You should not use an automated land-and-deploy workflow when a release requires manual approval gates, custom rollback logic, or infrastructure lacking canary deployment support. It suits automated, auditable promotion flows assuming standard CI-CD pipeline compatibility.