land-and-deploy

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

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/TarunTeja44/portfolio --skill land-and-deploy-tarunteja44
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/TarunTeja44/portfolio/tree/main/.agents/skills/land-and-deploy
Command: npx skills add https://github.com/TarunTeja44/portfolio --skill land-and-deploy-tarunteja44

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merging a PR is only half the job — you still need to wait for CI, watch the deploy, and confirm production is healthy. This Skill automates the entire post-PR release workflow so nothing ships broken or sits unverified. ## Core Features & Use Cases - Pre-merge readiness gate: Checks review staleness, test results, PR body accuracy, and documentation updates before allowing an irreversible merge, with an explicit confirmation report. - Automated merge and deploy tracking: Merges via GitHub CLI (auto-merge or squash), polls merge queues, detects deploy platforms (Vercel, Fly, Render, Netlify, Heroku, Railway) and GitHub Actions deploy workflows. - Production canary verification: Verifies the deployed site at a production URL and offers a revert path if health checks fail. - Use Case: After /ship creates a PR, run /land-and-deploy #123 https://myapp.com to merge it, wait for the Vercel deploy, and confirm the production site responds correctly. ## Quick Start Ask the assistant to land and deploy the current branch's pull request and verify production at your site's 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 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 your production URL.

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

It verifies review staleness against current HEAD, runs the project's free tests, checks recent 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.

Which deploy platforms does this workflow detect?

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

What happens if the production canary check fails after deploy?

The workflow flags the production health issue and offers to revert the merge. It treats canary failures as a stop condition rather than silently continuing, so broken deploys are surfaced immediately.

Can I use this without a pull request on the current branch?

No. If no PR exists for the branch, the workflow stops and tells you to run /ship first to create one. It also stops if the PR is closed, already merged, or has merge conflicts.