land-and-deploy

Merge a GitHub PR, wait for CI, deploy, and verify production health via canaries.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Land and deploy workflows remove the manual guesswork from merging PRs, waiting for CI, performing production deploys, and validating health with canaries, reducing delays and risk in shipping.

Core Features & Use Cases

  • Automates PR merge, CI wait, and production deploy.
  • Verifies production health with canary checks and automatic rollback when issues are detected.
  • Provides gatekeeping steps and post-deploy verification to ensure safe releases.
  • Works with the /ship workflow to take over once a PR is created for deployment.

Quick Start

Invoke land-and-deploy on a ready PR to automatically merge, deploy, and verify production health via 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 merging a PR, waiting for CI, and deploying to production?

Automating PR merge, CI checks, and production deploy is handled by enforcing safety gates that merge a ready PR, wait for CI, and trigger the deploy pipeline. This removes manual guesswork and reduces release delays.

How does canary health verification work during a production deploy?

Canary health verification works by coordinating with canary ramps and running production checks after deploying. It monitors application health during the rollout and can trigger an automatic rollback if issues are detected.

What is the best way to automatically rollback a failed production deployment?

The best way to rollback a failed production deployment is using an automated workflow that verifies production health via canaries and triggers a rollback when issues are detected, minimizing risk during releases.

Can I use this deployment workflow with an existing GitHub PR?

Yes, you can use this workflow with an existing GitHub PR. It applies when a GitHub PR exists and is ready to move from the /ship stage to live production, handling pre-merge checks before deploying.

Do I need any special dependencies to automate canary ramps and production checks?

No special dependencies are required to automate canary ramps and production checks. The workflow operates independently to enforce safety gates, coordinate canary ramps, and verify production health after merging your PR.