land-and-deploy

Merge pull requests, wait for CI, deploy, and verify canary health.

Updated Mar 29, 2026

Search Tags:#automation #ci-cd #canary #release-engineering #production-verification #pr-merge #land-and-deploy

Ready to run

npx skills add https://github.com/zzxtbeta/design-handbook --skill land-and-deploy-zzxtbeta

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/zzxtbeta/design-handbook/tree/main/.agents/skills/gstack/land-and-deploy
Command: npx skills add https://github.com/zzxtbeta/design-handbook --skill land-and-deploy-zzxtbeta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end release workflow by merging PRs, waiting for CI, deploying to production, and validating canary health.

Core Features & Use Cases

Merges the PR after CI success and coordinates the subsequent deploy.
Waits for deployment, applies canary health checks, and promotes rollout when healthy.
Takes over after /ship, enabling a streamlined land-and-deploy sequence for production readiness.

Quick Start

Run land-and-deploy on your current PR to merge, deploy, and verify production health with canaries.

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 pull request merges and deploy to production with canary verification?▼

Automating pull request merges and deploy to production involves merging PRs after CI success, waiting for deployment, and verifying production health via canary checks. This workflow coordinates the entire post-ship land-and-deploy sequence automatically.

What is a land-and-deploy workflow for release engineering?▼

A land-and-deploy workflow is an automated release engineering sequence that merges pull requests, waits for CI, deploys to production, and validates canary health to ensure production readiness before promoting a full rollout.

Can I use this automated deploy workflow with my GitHub-based repository?▼

Yes, this automated deploy workflow applies to GitHub-based repositories with a standard PR process. It requires repository access to pull requests, CI systems, and deployment health endpoints to execute properly.

How do I verify production health after deploying a merged pull request?▼

To verify production health after deploying a merged pull request, the workflow applies canary health checks and waits for deployment completion. It only promotes the rollout when the canary checks confirm the application is healthy.

What's the best way to coordinate CI success with production deployment automatically?▼

The best way to coordinate CI success with production deployment is using an automated workflow that merges PRs after CI passes, waits for the deployment to finish, and then runs canary health checks before promoting the release.

Do I need Bash execution access to automate the post-ship land-and-deploy sequence?▼

Yes, you need Bash execution access and prompt-based UX capabilities to run the post-ship land-and-deploy sequence, along with repository access to PRs, CI, and deployment health endpoints.