land-and-deploy

Automate post-PR merging, deployment, and canary health verification.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Land and deploy automates the post-PR workflow: merging, waiting for CI, deploying to production, and validating health with canaries.

Core Features & Use Cases

  • Auto-merge PRs after CI passes and trigger deployment with health checks.
  • Wait for CI, reconcile canary health signals, and verify production readiness before completion.
  • Supports multiple deployment targets and works after the /ship workflow to complete the release.

Quick Start

Run land-and-deploy to automatically merge the PR, wait for CI, deploy, and verify production health.

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 GitHub PR merge and deployment verification?

Automate PR merge and deployment verification by using a guided workflow that merges after CI passes, triggers deployment, and validates production health using canary checks.

How does canary health verification work after a PR merge?

Canary health verification works by reconciling production health signals after deployment, ensuring the release is stable before the workflow completes.

Do I need the GitHub CLI to automate my release process?

Yes, you need the GitHub CLI to execute this release process, along with accessible CI status checks and a configured deployment target.

Can I deploy to multiple targets after merging a PR?

Yes, you can deploy to multiple configured deployment targets after the PR is merged and CI status checks pass.

What is a deterministic release process for GitHub PRs?

A deterministic release process for GitHub PRs applies a single pre-merge readiness gate, then automatically merges, deploys, and validates production health to ensure consistent releases.

When should I use an automated canary deployment workflow?

Use an automated canary deployment workflow when your team needs a deterministic release process that waits for CI, deploys to production, and reconciles health signals before completion.