land-and-deploy

Merges pull requests, monitors CI deploys, and verifies production health via canary checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merging a PR and confirming the deploy actually reached production involves many fragile steps: waiting on CI, handling merge queues, detecting deploy workflows, and running health checks. This Skill automates that entire post-PR workflow with safety gates before the irreversible merge. ## Core Features & Use Cases - Pre-merge readiness gate: Checks review staleness, test evidence, CHANGELOG/VERSION updates, and PR body accuracy, then presents a readiness report requiring explicit confirmation before merging. - Merge and deploy orchestration: Resolves the repo's allowed merge method, tries auto-merge first, handles merge queues, and recovers safely from failed merge attempts using authoritative GitHub PR state. - Deploy verification: Detects the platform (Fly.io, Vercel, Netlify, Heroku, Railway, Render) and deploy workflows, offers staging-first deploys, and runs canary health checks against the production URL. - Use Case: After /ship creates a PR, say "land it" and the Skill validates readiness, merges, waits for the deploy workflow, and confirms production is healthy. ## Quick Start Ask the assistant to merge and deploy the current pull request 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 deploy to production automatically?

Invoke the skill with a phrase like "merge and deploy" or "land the PR". It runs readiness checks, merges via the repo's allowed method (squash, merge, or rebase), waits for the deploy workflow, and runs canary health checks against production.

What happens if the GitHub merge command fails?

The skill queries authoritative PR state with gh pr view before any retry. If the PR is already merged it captures the merge SHA and continues; if still open it checks auto-merge status; it never blindly retries a failed gh pr merge call.

Does it support merge queues and auto-merge?

Yes. It tries gh pr merge --auto first, detects when the PR enters a merge queue, and polls every 30 seconds for up to 30 minutes until the merge completes, reporting progress along the way.

Can I deploy to staging before production?

Yes. If a staging environment is detected from CLAUDE.md config, staging workflows, or preview deploys, the skill offers a staging-first option that runs the same health checks on staging before promoting to production.

What checks run before the merge is allowed?

A readiness gate verifies code review staleness, test evidence (unit, E2E, LLM evals), CHANGELOG and VERSION updates, and PR body accuracy. Failing tests are blockers; other issues surface as warnings requiring user confirmation.

Which deploy platforms are detected?

The skill auto-detects Fly.io, Render, Vercel, Netlify, Heroku, and Railway from their config files, plus GitHub Actions deploy workflows. Persisted configuration in CLAUDE.md takes precedence over auto-detection.