land-and-deploy

Automate PR merge, CI wait, production deployment, and canary health checks.

Updated Aug 2, 2025
One-click install
npx skills add https://github.com/JovieInc/Jovie --skill land-and-deploy-jovieinc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/JovieInc/Jovie/tree/main/.claude/skills/gstack/land-and-deploy
Command: npx skills add https://github.com/JovieInc/Jovie --skill land-and-deploy-jovieinc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Land-and-deploy automates the end-to-end process of merging a PR, waiting for CI, triggering deployment, and validating production health via canary checks. This reduces risk and accelerates shipping by ensuring checks are green before promoting changes to users.

Core Features & Use Cases

  • Pre-merge readiness gate collects evidence and confirms CI/merge readiness.
  • Auto-merge or manual merge with proper fallback and rollback options.
  • Deployment verification with canary health checks across detected platforms.
  • Rollback and containment guidance if deployment health is not satisfactory.
  • Supports configurable deploy strategies and environments, plus a structured readiness report.

Quick Start

Run land-and-deploy to merge the PR, wait for CI, deploy to production, and verify 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 a GitHub PR merge, wait for CI, and deploy to production?

Automating a GitHub PR merge, CI wait, and production deploy requires a release engineering workflow that enforces a pre-merge readiness gate, monitors CI, and verifies deployment health. This automates the end-to-end process to reduce risk and accelerate shipping.

What is the best way to run canary health checks after merging a PR?

The best way to run canary health checks after a PR merge is using an automated deployment verification workflow. It validates production health across detected platforms and provides rollback guidance if deployment health is unsatisfactory.

Does land-and-deploy support rollback options if production deployment fails?

Yes, land-and-deploy supports rollback and containment guidance if deployment health is not satisfactory. It enforces deploy verification and rollback options to protect production stability during release engineering workflows.

Can I use configurable deploy strategies and environments for release engineering?

Yes, you can use configurable deploy strategies and environments. The workflow supports auto-merge or manual merge with proper fallback, guiding deployment and pre-production validation to ensure checks are green before promoting changes.

How does a pre-merge readiness gate work for continuous deployment?

A pre-merge readiness gate for continuous deployment works by collecting evidence and confirming CI and merge readiness. This gate ensures all checks are green before promoting changes to users, reducing deployment risk.

When do I need automated PR landing with deployment verification?

You need automated PR landing with deployment verification when a controlled merge, guided deployment, and pre-production validation are required. It targets release engineering workflows to protect production stability during releases.