land-and-deploy

Orchestrates PR merge, CI wait, and production deployment after canary health checks pass.

Updated Apr 13, 2026

Search Tags:#devops #production #ci #canary #pr-merge #land-deploy

Ready to run

npx skills add https://github.com/legotec73/gstack --skill land-and-deploy-legotec73

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Land and deploy orchestrates merging a pull request, waiting for continuous integration to complete, and deploying to production only after production health is verified via canary checks.

Core Features & Use Cases

Automates PR merge, CI validation, and production deployment.
Canary health checks ensure safe production rollout.
Suitable for teams that want end-to-end deployment automation from code review to live release.

Quick Start

Run land-and-deploy to merge the PR, wait for CI, and deploy to production after Canary checks.

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 validation, and production deployment in one step?▼

You can automate PR merge, CI validation, and production deployment by orchestrating the workflow end-to-end. This process merges pull requests, waits for continuous integration to complete, and deploys to production only after canary health checks pass.

What are canary health checks and when do I need them for production rollout?▼

Canary health checks verify production stability during a gradual rollout. You need them when automating end-to-end deployments to ensure a pull request triggers a production release only when all system health checks succeed.

How does canary deployment work with continuous integration?▼

Canary deployment works with continuous integration by pausing the production rollout after a pull request merge. The system waits for CI to complete successfully, then promotes the change to production after verifying canary health checks.

Do I need a specific CI system to automate PR merges and canary deployments?▼

You need alignment with your existing pull request workflow, CI system, and production health checks. The deployment automation requires your continuous integration system to complete successfully before canary checks trigger the production release.

What happens if CI fails after a pull request is merged?▼

If continuous integration fails after a pull request is merged, the deployment to production is blocked. The system ensures a PR triggers a deployment only when all CI checks succeed before proceeding to canary health verification.

When should I not use automated end-to-end deployment automation?▼

You should avoid automated end-to-end deployment if your environment lacks canary testing capabilities or reliable production health checks, as the system requires these to safely promote changes from code review through live release.