land-and-deploy

Merge a prepared pull request and deploy with canary verification.

8|2|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/MFS-code/gstack --skill land-and-deploy-mfs-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/MFS-code/gstack/tree/main/land-and-deploy
Command: npx skills add https://github.com/MFS-code/gstack --skill land-and-deploy-mfs-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the stress and guesswork of landing a prepared pull request and getting it safely into production by automating merge, deploy monitoring, and post-deploy canary health checks.

Core Features & Use Cases

  • Merge-ready landing: Merges a PR created by /ship after verifying PR state, CI status, and merge conflicts.
  • Pre-merge readiness gate: Stops for a final user confirmation after collecting evidence (reviews freshness, test results, doc-release signals, and PR body accuracy).
  • Deploy verification + canary checks: Detects the deploy strategy (GitHub Actions / platform / production URL) and runs the right depth of verification based on what changed.

Quick Start

Invoke this skill when you are ready to ship by typing /land-and-deploy to merge the PR, deploy it, and verify production health with canary checks.

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 pull request and deploy it to production safely?

To merge a pull request and deploy to production safely, automate the workflow by validating PR state, gating on CI checks, and running post-deploy canary verification to confirm production health. This process requires explicit user confirmation before merging to remove guesswork from release management.

What is a pre-merge readiness gate in CI/CD deployment?

A pre-merge readiness gate in CI/CD deployment halts the automated release process to collect evidence like review freshness, test results, and doc-release signals, requiring explicit user confirmation before merging a pull request to ensure production safety.

How does post-deploy canary verification work for GitHub pull requests?

Post-deploy canary verification for GitHub pull requests works by detecting the deploy strategy, such as GitHub Actions or a production URL, and running verification checks scaled to the diff scope to monitor production health after the merge completes.

Do I need GitHub CLI access to automate pull request deployment?

Yes, you need GitHub CLI access to automate pull request deployment, as it is required for robust PR state validation, checking CI status, and executing the merge operation during the release management workflow.

Can I deploy a staged pull request without manual confirmation?

No, you cannot deploy a staged pull request without manual confirmation, because the pre-merge readiness gate halts the process after collecting evidence like test results and review freshness to require explicit user confirmation before proceeding.