land-and-deploy

Merge PRs, wait for CI, deploy, and verify production health via canary checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Land and deploy workflow that merges PRs, waits for CI, deploys, and verifies production health via canary checks.

Core Features & Use Cases

  • Merges the PR and waits for CI to pass before deployment
  • Deploys to production and validates health with canary checks
  • Takes over after /ship: creates the PR and manages the end-to-end release
  • Use when preparing a release: "merge", "land", "deploy", "ship it to production"

Quick Start

Run /land-and-deploy to merge the PR, deploy to production, and verify 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?

To automate the end-to-end release flow, you can use a land-and-deploy workflow that merges a PR, waits for CI to pass, deploys, and verifies production health via canary checks. Running the /land-and-deploy command manages this entire sequence automatically.

What does a canary deployment verification check after a production release?

Canary deployment verification checks production health after a release to ensure stability. It validates the newly merged code by monitoring specific canary checks, confirming the deployment operates correctly in the live environment before completing the flow.

Do I need the GitHub CLI to automate my pull request release workflow?

Yes, automating the pull request release workflow requires an authenticated GitHub CLI. You also need an active PR branch and access to repository workflows to successfully merge, deploy, and verify production health.

Can I manually override an automated PR deploy and canary verification flow?

Yes, you can manually override or initiate the automated PR deploy and canary verification flow using specific commands. The workflow supports manual triggers via /ship to create the PR, and /land-and-deploy to manage the end-to-end release.

What is the best way to manage a gated deploy verification in a CI pipeline?

The best way to manage gated deploy verification in a CI pipeline is using an automated release flow that handles pre-flight checks and first-run validation. This ensures CI passes before production deployment and triggers health verification automatically.