land-and-deploy

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

107|7|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/no-session/pstack --skill land-and-deploy-no-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/no-session/pstack/tree/main/land-and-deploy
Command: npx skills add https://github.com/no-session/pstack --skill land-and-deploy-no-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merging a PR and confirming the deploy actually worked is a manual, error-prone ritual: watching CI, picking a merge method, waiting for the deploy workflow, then checking production. This Skill automates that entire release sequence with readiness gates and health verification. ## Core Features & Use Cases - Automated merge pipeline: Detects the PR from the current branch, validates its state, waits for CI, and merges using the repo's configured method (squash, merge, or rebase). - Pre-merge readiness gate: Checks review status, tests, CHANGELOG, and PR accuracy before anything irreversible happens. - Deploy verification: Detects the hosting platform (Fly.io, Render, Vercel, Netlify, Heroku, Railway), waits for the deploy workflow, and runs monitor health checks against the production URL, offering revert on failure. - First-run dry run: On first use for a project, it validates deploy infrastructure and shows exactly what will happen before touching anything. - Use Case: After /ship creates PR #42, run /land-and-deploy #42 https://myapp.com to merge it, wait for the Fly.io deploy, and verify the site returns healthy responses. ## Quick Start Type /land-and-deploy to merge the PR for your current branch, wait for the deploy, and verify production health automatically.

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 detects the PR from your branch, waits for CI, merges using the repo's configured method, waits for the deploy workflow, and runs health checks against production.

What deployment platforms does this release workflow support?

It 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. It also detects GitHub Actions deploy workflows and persisted config in CLAUDE.md.

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

No. GitLab support is not implemented. The skill stops with a message telling you to run /ship to create the MR, then merge manually through the GitLab web UI.

What happens if CI fails or the deploy breaks production?

CI failures, merge conflicts, and permission errors stop the workflow before merging. If the deploy workflow fails or monitor checks detect production health issues, the skill stops and offers a revert option.

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

On first use for a project, it validates deploy infrastructure, tests platform CLI commands, checks production URL reachability, and shows exactly what will happen before merging. It re-runs this validation if the deploy configuration changes.