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/Simon-YHKim/eject-button --skill land-and-deploy-simon-yhkim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/Simon-YHKim/eject-button/tree/main/.claude/skills/land-and-deploy
Command: npx skills add https://github.com/Simon-YHKim/eject-button --skill land-and-deploy-simon-yhkim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Merging a PR and confirming the deploy actually worked is a manual, error-prone process: watching CI, picking the right merge method, waiting on deploy workflows, and checking production health. This Skill automates the entire post-PR release sequence with safety gates before anything irreversible happens. ## Core Features & Use Cases - Automated merge pipeline: Detects the PR from the current branch, checks CI status and merge conflicts, waits for pending checks, and merges using the repo's configured method (squash, merge, or rebase). - Pre-merge readiness gate: Reviews code review staleness, test results, CHANGELOG updates, and PR accuracy before merging, with an optional inline quick review of the diff. - Deploy verification: Detects the deploy platform (Fly.io, Render, Vercel, Netlify, Heroku, Railway), waits for the deploy workflow, and runs canary health checks against the production URL, offering revert on failure. - Use Case: After running /ship to create a PR, invoke this Skill to merge it, wait for the GitHub Actions deploy to finish, and get a verdict on whether production is healthy. ## Quick Start Type /land-and-deploy to merge the PR for the current branch and verify the production deploy, optionally passing a PR number like /land-and-deploy #123 or a verification URL.

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 checks CI status, runs a pre-merge readiness gate, 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 auto-detects Fly.io (fly.toml), Render (render.yaml), Vercel (vercel.json), Netlify (netlify.toml), Heroku (Procfile), and Railway (railway.json), plus GitHub Actions deploy workflows. Platform CLIs are used when installed, with HTTP health checks as fallback.

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

No. GitLab support is not implemented. The skill detects the platform from the git remote and stops with a message telling you to merge manually via the GitLab web UI after running /ship to create the MR.

What happens if CI fails or the deploy breaks production?

The skill stops before merging if CI fails or merge conflicts exist. If the deploy workflow fails or canary checks detect production health issues, it flags the problem and offers to revert the merge.

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

On first run for a project, it detects and validates your deploy infrastructure, tests platform commands, and shows a confirmation table before touching anything. The configuration fingerprint is saved and the dry run re-triggers automatically if your deploy setup changes.