land-and-deploy

This Skill automates the end-to-end release flow by merging your PR, waiting for CI to pass, deploying to production, and validating canary health automatically. It eliminates manual handoffs and reduces time-to-production.

Canary-based validation for production deployments checks production health by routing a subset of traffic to the new version before finalizing the release. This workflow includes automated rollback hooks to protect production if canary health checks fail.

Before automating PR merge and production deployment, you need an authenticated Git hosting account, an open PR on the current branch, and access to CI status and production canaries. These prerequisites allow the workflow to orchestrate merge, deploy, and verify steps.

To verify production health after merging a PR, the workflow deploys your changes to production and runs canary health checks automatically. It ensures production readiness before finalizing the release and provides automated rollback hooks if health checks fail.

Automated deployment waits for CI to finish before proceeding. The workflow monitors CI status on your current branch after merging the PR, ensuring CI passes before deploying to production and validating canary health.

You should not use an automated merge and deploy workflow if you lack an authenticated Git hosting account, an open PR on the current branch, or access to CI status and production canaries. The workflow requires these elements to orchestrate merge, deploy, and verify steps safely.