land-and-deploy

Automate PR merge, CI wait, and production canary verification.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/MissTully/Gstack --skill land-and-deploy-misstully
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/MissTully/Gstack/tree/main/land-and-deploy
Command: npx skills add https://github.com/MissTully/Gstack --skill land-and-deploy-misstully

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Land and deploy processes are error-prone and slow; this skill automates PR merge, CI wait, and production canary verification to deliver reliable releases.

Core Features & Use Cases

  • End-to-end release orchestration: merges PRs, waits for CI, and triggers production deployment with canaries.
  • Safeguarded rollout: monitors health signals and can halt or roll back if issues are detected.
  • Smooth handoff from ship to production: ensures the PR that ships becomes a live deployment with verified success.

Quick Start

Trigger a land-and-deploy flow on the current pull request.

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 wait, and production deployment in one workflow?

Automated PR merge, CI wait, and deployment orchestration handles the end-to-end release workflow by merging pull requests, waiting for CI checks, and triggering production deployment with canary-based health verification.

How does canary-based health verification work during an automated deployment?

Canary-based health verification monitors production health signals after deployment triggers, automatically halting or rolling back the release if issues are detected across staging and production environments.

Can I use automated canary rollouts to safeguard releases across staging and production?

Automated canary rollouts safeguard releases by monitoring health signals across staging and production, halting or rolling back deployments if issues are detected during the verification gates.

What is the best way to ensure a merged PR becomes a verified live deployment?

End-to-end release orchestration ensures a merged PR becomes a verified live deployment by automating the handoff from ship to production with continuous CI wait and canary health checks.

When should I use automated rollback gates during a production canary deployment?

Automated rollback gates should be used during production canary deployments whenever health verification detects issues, ensuring reliable releases by halting problematic rollouts automatically.

Does land-and-deploy require a specific Git workflow to automate canary releases?

Land-and-deploy is designed for teams using Git workflows who want automated land, CI wait, and canary-based health checks across staging and production environments.