land-and-deploy

Name: land-and-deploy
Availability: InStock
Author: makyua-san

Automates Git-based PR merge, CI wait, production deploy, and canary health checks.

Updated Apr 5, 2026

Search Tags:#ci-cd #canary #pr-workflow #production-deploy #merge-pr #land-and-deploy

Ready to run

npx skills add https://github.com/makyua-san/usecase-agent --skill land-and-deploy-makyua-san

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/makyua-san/usecase-agent/tree/main/.claude/skills/land-and-deploy
Command: npx skills add https://github.com/makyua-san/usecase-agent --skill land-and-deploy-makyua-san

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the end-to-end merge, deploy, and post-deploy verification process for PRs, reducing manual handoffs and risk.

Core Features & Use Cases

Automatically merges PRs after CI success and canary checks pass.
Deploys to production with canary health verification and automated rollback if issues arise.
Takes over after /ship by creating the PR and confirming production health.

Quick Start

Run the land-and-deploy flow on a PR branch to merge, wait for CI, and deploy to production with 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 merging a PR, waiting for CI, and deploying to production?▼

Automating PR merge, CI verification, and production deploy is handled by orchestrating the end-to-end land-and-deploy workflow, which merges Git-based PRs after CI success and deploys with canary health checks. It reduces manual handoffs and deployment risk.

What is a canary deploy workflow with automated rollback?▼

A canary deploy workflow with automated rollback is a production deployment process that verifies application health checks during a staged rollout. If issues arise during the canary checks, the system automatically reverts the deployment to maintain production stability.

How do I deploy to production only after CI checks pass on a merged PR?▼

To deploy to production after CI checks pass on a merged PR, the land-and-deploy workflow automatically waits for CI success on the Git branch, merges the PR, and then triggers the production deployment with post-merge health verification.

Does the gstack framework support post-merge governance and health verification?▼

Yes, the gstack framework supports post-merge governance and health verification by coordinating end-to-end deployment. It takes over after creating the PR, confirms production health through canary checks, and ensures automated rollback if deployment issues arise.

When should I not use an automated end-to-end merge and canary deploy workflow?▼

You should avoid automated end-to-end merge and canary deploy workflows when your production environment lacks health monitoring endpoints for canary checks, or when your deployment strategy requires manual approval gates outside of CI success and automated rollback capabilities.