land-and-deploy

Coordinate PR merge, CI wait, deployment, and canary verification in GitHub workflows.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/Andy-HNU/AndyClaw --skill land-and-deploy-andy-hnu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/Andy-HNU/AndyClaw/tree/main/skills/gstack-land-and-deploy
Command: npx skills add https://github.com/Andy-HNU/AndyClaw --skill land-and-deploy-andy-hnu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the risky end-to-end release workflow by merging PRs, waiting for CI, performing deployments, and validating production health with canaries, reducing manual toil and errors.

Core Features & Use Cases

  • End-to-end release orchestration: pre-merge checks, PR merge automation, deployment triggering, canary health verification, and safe rollback options.
  • Canary-based production validation: verify health signals before promoting changes to full traffic.
  • Post-merge decision support: provides guardrails for failures and conflicts, with automated revert options if issues arise.

Quick Start

Run /land-and-deploy to automatically detect the PR from your current branch and start the end-to-end release process.

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

PR merge, CI checks, and deployment are coordinated by land-and-deploy to safely promote changes end-to-end. It merges PRs, waits for CI, triggers deployments, and validates production health with canaries.

How does canary-based production verification work for GitHub releases?

Canary-based production verification checks health signals before promoting changes to full traffic. Land-and-deploy validates production health during deployment and provides rollback guidance if issues arise.

Do I need GitHub CLI access to automate PR merge and deployment?

Yes, GitHub CLI access is required for land-and-deploy to orchestrate the workflow. It also requires gstack tooling to handle pre-merge checks, post-merge checks, and canary-based production verification.

What happens if a production deployment fails after a PR merge?

If production deployment fails after a PR merge, land-and-deploy provides post-merge decision support with guardrails for failures and conflicts, including automated revert options to safely roll back changes.

Can I automatically detect a pull request from my current branch for release?

Yes, running the land-and-deploy command automatically detects the pull request from your current branch and starts the end-to-end release process, handling pre-merge checks, deployment, and canary verification.