land-and-deploy

Automating PR merge, CI wait, and production deployment requires a workflow that merges PRs, waits for CI, deploys, and validates canary health. This Skill streamlines that end-to-end release process for GitHub-based pipelines.

Canary verification in a production deployment validates application health by routing traffic incrementally to new code. This workflow observes deployment health and provides rollback options if canary checks fail.

A CLAUDE.md file is needed to guide deployment decisions in this workflow. The process reads configuration cues from CLAUDE.md to inform how the automated PR merge and canary deployment are executed.

You can roll back a production deployment if canary health checks fail. The workflow observes deployment health post-deploy and provides rollback options to restore the previous stable state.

The best way to enforce pre-merge checks before a GitHub CI deployment is to use an automated workflow that waits for CI to pass before proceeding. This process enforces those checks before merging and deploying.