land-and-deploy

Automated PR merge and pipeline wait merges approved release PRs and automatically monitors CI/CD pipelines until deployment completes, eliminating manual monitoring and ensuring code lands safely.

Production canary verification runs post-deploy health checks against canary systems to confirm the release is healthy before marking the workflow complete, preventing broken code from persisting unnoticed.

Yes, automating end-to-end release workflows requires access to git repositories, CI/CD pipeline status endpoints, and production canary check systems to safely execute the full merge-to-production process.

The best way to safely ship approved PRs without manual monitoring is an automated workflow that merges PRs, waits for CI/CD pipelines, and runs production canary checks to verify health end-to-end.

Yes, after creating a release PR, this skill handles the full merge-to-production workflow by merging the PR, waiting for CI and deployment to finish, and verifying production health via canary checks.

Manually merging PRs and verifying production health leads to broken deployments because waiting for CI pipelines and running post-deploy checks manually is time-consuming, error-prone, and prone to missed production issues.