land-and-deploy

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merging a PR and confirming the deploy actually reached production is a slow, error-prone manual loop of watching CI, waiting on deploy pipelines, and pinging health endpoints. This Skill automates the full post-PR release sequence and gives a clear verdict on production health. ## Core Features & Use Cases - Automated PR merge: Detects the PR for the current branch (or a specified PR number), validates its state, runs a pre-merge readiness gate covering reviews, tests, and docs, then merges using the repo's configured method. - Deploy detection and monitoring: Detects the deploy platform (Fly.io, Render, Vercel, Netlify, Heroku, Railway) from config files and CLAUDE.md, then waits for CI and deploy workflows to finish. - Production canary verification: Runs health checks against the production URL after deploy and offers a revert path if failures are detected. - First-run dry run: On first use for a project, walks through detected deploy infrastructure and validates commands before touching anything irreversible. - Use Case: After running /ship to open a PR, invoke this Skill to merge it, wait for the Fly.io deploy to complete, and verify the production URL returns healthy responses. ## Quick Start Ask the assistant to run /land-and-deploy to merge the current branch's PR, wait for the 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 merge a PR and verify the deploy automatically?

Run /land-and-deploy after creating a PR. It detects the PR from your current branch, runs a pre-merge readiness gate, merges it, waits for CI and the deploy workflow, then 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, vercel.json, netlify.toml, Procfile, and railway.json. 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 with a message telling you to create the MR with /ship and merge it manually through the GitLab web UI.

What happens if the production canary check fails after deploy?

The skill reports the health issue and offers to revert the change. Deploy failures and canary failures are explicit stop points where the user decides whether to roll back.

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

On first use for a project it detects deploy infrastructure, validates that commands actually work, and shows the full plan before doing anything irreversible. It re-triggers the dry run if the deploy configuration changes later.

What are the prerequisites for running land-and-deploy?

You need an authenticated GitHub CLI (gh auth login), an open PR for the current branch (typically created by /ship), and a detectable deploy setup. It stops with guidance if any of these are missing.