land-and-deploy

Merges GitHub pull requests, waits for CI and deploy, and verifies production health via canary checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merging a PR and confirming the deploy actually reached production involves tedious manual polling of CI checks, merge queues, and health endpoints, with real risk of shipping broken code. This Skill automates the entire post-PR workflow with a safety gate before the irreversible merge. ## Core Features & Use Cases - Pre-merge readiness gate: Builds a readiness report covering review staleness, test results, PR body accuracy, and CHANGELOG/VERSION updates, then asks for explicit confirmation before merging. - Automated merge and queue handling: Uses GitHub CLI to merge with auto-merge or squash, polls merge queues, and handles CI waits with timeouts. - Deploy detection and canary verification: Detects the hosting platform (Fly, Render, Vercel, Netlify, Heroku, Railway) from config files and verifies production health, offering revert on failure. - Use Case: After running /ship to create a PR, invoke this Skill to merge it, wait for the deploy workflow, and get a clear verdict on whether production is healthy. ## Quick Start Type /land-and-deploy with an optional PR number and production URL to merge the current branch's PR and verify the deployment.

Frequently Asked Questions about land-and-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I merge a GitHub PR and verify the deployment automatically?

Run /land-and-deploy with an optional PR number and production URL. It checks CI status, runs a pre-merge readiness gate, merges via GitHub CLI, waits for the deploy workflow, and runs canary health checks against your production URL.

What happens before the PR is merged?

A pre-merge readiness gate collects evidence on review staleness, free and E2E test results, PR body accuracy, and CHANGELOG/VERSION updates. It presents a readiness report and asks for explicit confirmation before the irreversible merge.

Which deployment platforms are supported for verification?

The Skill auto-detects Fly.io, Render, Vercel, Netlify, Heroku, and Railway from config files like fly.toml, render.yaml, or vercel.json. It can also read a persisted deploy configuration from CLAUDE.md.

What happens if CI fails or the deploy is unhealthy?

If CI checks fail or merge conflicts exist, the workflow stops and shows the failures. If the deploy workflow fails or canary checks detect production health issues, it stops and offers to revert the change.

Can I use this without creating a PR first?

No. The Skill expects an existing PR for the current branch, typically created by the /ship skill. If no PR is found, it stops and instructs you to run /ship first.