land-and-deploy

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

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/VertaKhan/cs_gstack --skill land-and-deploy-vertakhan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/VertaKhan/cs_gstack/tree/main/.claude/skills/gstack/land-and-deploy
Command: npx skills add https://github.com/VertaKhan/cs_gstack --skill land-and-deploy-vertakhan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merging a PR is only half the job — you still have to wait for CI, watch the deploy, and confirm production is actually healthy. This Skill automates the post-PR release workflow so merges don't sit in queue and broken deploys get caught immediately. ## Core Features & Use Cases - Automated PR merge: Detects the PR from the current branch (or a given #NNN), validates state, checks reviews/tests/docs readiness, and merges using the repo's configured method. - Deploy monitoring: Detects the deploy platform (Fly.io, Render, Vercel, Netlify, Heroku, Railway) and GitHub Actions deploy workflows, then waits for deployment to complete. - Production canary verification: Checks production health at a given URL after deploy and offers a revert path if issues are detected. - Use Case: After running /ship to open a PR, invoke /land-and-deploy #42 https://myapp.com to merge the PR, wait for the deploy workflow, and verify the live site responds correctly. ## Quick Start Type /land-and-deploy with an optional PR number and production URL to merge the pull request 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 detects the PR from your branch, runs pre-merge readiness checks, merges, waits for the deploy workflow, and runs canary health checks against production.

What deploy platforms does this release workflow support?▼

It auto-detects Fly.io, Render, Vercel, Netlify, Heroku, and Railway from config files like fly.toml, render.yaml, or vercel.json, plus GitHub Actions deploy workflows. Persisted settings in CLAUDE.md take priority over auto-detection.

Does land-and-deploy work with GitLab merge requests?▼

No. GitLab support is not implemented; the skill stops and instructs you to merge manually via the GitLab web UI. It currently requires GitHub with an authenticated gh CLI.

What happens if the production canary check fails after deploy?▼

The skill stops and offers a revert path when canary checks detect production health issues. It treats deploy verification failures as a gate, so a broken release is surfaced immediately rather than silently shipped.

Why does land-and-deploy run a dry-run validation on first use?▼

On the first run for a project it detects deploy infrastructure, validates that platform commands actually work, and shows the full plan before merging. It re-triggers this dry run if the deploy configuration changes after a confirmed deploy.