land-and-deploy

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

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/dhnpmp-tech/project-agent --skill land-and-deploy-dhnpmp-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/dhnpmp-tech/project-agent/tree/main/.claude/skills/gstack/land-and-deploy
Command: npx skills add https://github.com/dhnpmp-tech/project-agent --skill land-and-deploy-dhnpmp-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merging a PR and confirming the deploy actually reached production is a manual, error-prone process involving CI polling, merge queues, and post-deploy verification. This Skill automates the entire land-and-deploy sequence with a pre-merge readiness gate so broken or unreviewed code never ships silently. ## Core Features & Use Cases - Pre-merge readiness gate: Checks review staleness, test results, E2E runs, PR body accuracy, and CHANGELOG/VERSION updates, then presents a readiness report requiring explicit confirmation before merging. - Automated merge and deploy tracking: Uses the GitHub CLI to merge with auto-merge or squash, polls merge queues, detects deploy platforms (Fly, Render, Vercel, Netlify, Heroku, Railway), and waits for deploy workflows. - Production canary verification: Verifies the deployment at a provided URL and offers a revert path if health checks fail. - Use Case: After running /ship to create a PR, invoke this Skill to merge PR #123, wait for CI, and confirm the new version is live at your production URL. ## Quick Start Ask the agent to land and deploy the current branch's pull request and verify production at your site 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?

Invoke the skill with an optional PR number and production URL. It checks CI status, runs a pre-merge readiness gate, merges via gh pr merge, waits for the deploy workflow, and runs canary checks against the URL you provided.

What does the pre-merge readiness gate check before merging?

It verifies review staleness against current HEAD, runs the project's free tests, checks same-day E2E and LLM eval results, validates PR body accuracy against actual commits, and confirms CHANGELOG and VERSION updates. Blockers like failing tests stop the merge.

Does it support merge queues and auto-merge on GitHub?

Yes. It first attempts gh pr merge --auto --delete-branch, falling back to squash merge if auto-merge is unavailable. When a merge queue is active, it polls the PR state every 30 seconds for up to 30 minutes until merged.

Which deploy platforms can it detect for production verification?

It reads persisted deploy configuration from CLAUDE.md or auto-detects platforms from config files: fly.toml, render.yaml, vercel.json, netlify.toml, Procfile, and railway.json. It also scans GitHub Actions workflows for deploy pipelines.

What happens if the production canary check fails after deploy?

The skill stops and reports the production health issue, then offers a revert path. Deploy workflow failures and canary failures are explicit stop conditions rather than silent passes.

Why does the skill stop when no PR exists for the current branch?

It is designed to take over after a PR-creation step such as /ship. Without an open PR there is nothing to merge, so it instructs you to create the PR first rather than attempting to create one itself.