land-and-deploy

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

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

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 actually works. This Skill automates the entire post-PR release workflow so you get a clear verdict instead of staring at a deploy queue. ## Core Features & Use Cases - Automated merge pipeline: Detects the PR from your current branch, validates its state, and merges using the repo's configured merge method. - Deploy infrastructure detection: Identifies platforms like Fly.io, Vercel, Netlify, Heroku, Railway, and Render, with a first-run dry run that validates commands before touching production. - Production verification: Waits for CI and deploy workflows, then runs canary health checks against your production URL, offering a revert path if issues are detected. - Use Case: After running /ship to create a PR, invoke this Skill to merge it, monitor the deploy, and confirm your live site is healthy — all in one continuous workflow. ## Quick Start Type /land-and-deploy with your production URL to merge the current branch's PR and verify the deploy.

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 deploy automatically?

Run /land-and-deploy after creating a PR. It detects the PR from your current branch, checks CI status, merges using the repo's configured method, waits for the deploy workflow, and runs canary health checks against your production URL.

What deploy platforms does this release workflow support?

It detects Fly.io, Render, Vercel, Netlify, Heroku, and Railway from config files like fly.toml, render.yaml, vercel.json, netlify.toml, Procfile, and railway.json. It also detects deploy workflows in .github/workflows and can read persisted config from CLAUDE.md.

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

No. GitLab support is not implemented. The skill stops with a message telling you to run /ship to create the MR, then merge manually through the GitLab web UI. It currently requires GitHub CLI (gh) authentication.

What happens if the deploy fails or production health checks detect issues?

The skill stops and offers a revert path. Deploy workflow failures and canary-detected production health issues are treated as stop conditions, so you can decide whether to roll back before users are affected.

Why does land-and-deploy run a dry run the first time?

On first run for a project, it performs a dry run to detect deploy infrastructure, validate that commands actually work, and show exactly what will happen before merging. It re-triggers this validation if your deploy configuration changes later.