land-and-deploy

Merge pull requests, run CI, deploy, and verify canary health.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/Jesse-L-M/scz-target-engine --skill land-and-deploy-jesse-l-m
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/Jesse-L-M/scz-target-engine/tree/main/.claude/skills/gstack/land-and-deploy
Command: npx skills add https://github.com/Jesse-L-M/scz-target-engine --skill land-and-deploy-jesse-l-m

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Land and deploy workflow. Merges the PR, waits for CI and deploy, verifies production health via canary checks. Takes over after /ship creates the PR. Use when: "merge", "land", "deploy", "merge and verify", "land it", "ship it to production". (gstack)

Core Features & Use Cases

  • End-to-end release orchestration: merge PR, wait for CI, trigger deploy, and validate production health with canaries.
  • Post-ship takeover: handles deployment handoff after PR creation and ensures a production-ready state.
  • Guardrails and readiness: provides pre-merge and canary health checks with clear readiness gates and rollback paths.

Quick Start

Run the land-and-deploy skill to automatically merge the PR, wait for CI, deploy, and verify production health via canaries.

Frequently Asked Questions about land-and-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate merging a PR and deploying to production safely?

To automate merging a PR and deploying to production safely, you can coordinate the end-to-end release by merging the PR, waiting for CI, triggering deploy pipelines, and running canary health checks with safe fallbacks.

What is a canary health check in a production deployment workflow?

A canary health check in a production deployment workflow validates production health after deploying, providing clear readiness gates and rollback paths to ensure the release is stable before completing the process.

How do I wait for CI to pass before merging a pull request?

You can wait for CI to pass before merging a pull request by using pre-merge validation that checks GitHub CLI auth and runs a first-run dry-run, ensuring CI completes successfully before the merge executes.

Can I deploy a specific PR number to production instead of my current branch?

Yes, you can deploy a specific PR number to production instead of your current branch. The deployment workflow supports auto-detection of the PR from the current branch or accepting explicit PR numbers for validation.

What happens if production canary checks fail during a deployment?

If production canary checks fail during a deployment, the workflow implements safe fallbacks and clear readiness gates to halt the process, preventing a bad release from fully impacting production.

Do I need a PR already created to run a merge and deploy workflow?

Yes, you need a PR already created to run a merge and deploy workflow. The workflow takes over after PR creation, handling the deployment handoff to ensure a production-ready state.