land-and-deploy

Merge PRs, wait for CI, deploy to production, and validate health via canary checks.

Updated Apr 22, 2026

Search Tags:#workflow #deploy #ci #canary #pull-request #land

Ready to run

npx skills add https://github.com/diiviikk5/rezops --skill land-and-deploy-diiviikk5

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/diiviikk5/rezops/tree/main/land-and-deploy
Command: npx skills add https://github.com/diiviikk5/rezops --skill land-and-deploy-diiviikk5

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Land and deploy automates the end-to-end lifecycle of merging a PR, waiting for CI, deploying to production, and validating production health via canary checks. It takes over after /ship creates the PR, enabling a reliable, auditable release flow with minimal manual intervention.

Core Features & Use Cases

Automatically merges PRs, waits for CI to pass, and deploys to production.
Verifies production health through canary checks and automatic handoff after /ship creates the PR.
Suitable for teams who want a hands-off, auditable release workflow from PR to production.

Quick Start

Create a PR and run land-and-deploy to merge, deploy, and validate production health.

Frequently Asked Questions about land-and-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate PR merge, CI checks, and production deployment in one workflow?▼

Automated release orchestration merges your PR, waits for CI to pass, and deploys to production with health checks. This handles the entire ship-to-production handoff with minimal manual intervention.

What is a canary check in a production deployment workflow?▼

Canary checks validate production health after deploying by monitoring traffic and metrics. They serve as automated gating to ensure the new release is stable before completing the handoff.

How do I set up end-to-end release orchestration from PR merge to production?▼

End-to-end release orchestration starts by merging the PR, waiting for CI, deploying to production, and running canary checks. Create a PR and trigger the workflow to automate the full lifecycle.

Can I automate production health validation after merging a pull request?▼

Yes, production health validation is automated through canary checks after the PR merge and deployment. The workflow waits for CI to pass, deploys, and then verifies stability before completing.

Does automated release orchestration work without manual intervention after creating a PR?▼

Automated release orchestration is designed for hands-off operation after the PR is created. It handles merging, CI gating, production deployment, and canary validation automatically for an auditable release flow.

What are the limitations of automating merge and deploy workflows with canary checks?▼

This release workflow applies specifically to flows starting from merge or land actions handling the ship-to-production handoff. It does not cover initial PR creation, which must be handled separately beforehand.