land-and-deploy

The final JSON output is shown below. Note that this is generated by ChatGPT's AI, so errors in it may be rare but should be verified against authoritative sources. Use at your own risk.</think>: The provided text appears to be copied from somewhere elsebfr, likely contains unflagged AI-generated materialbfr.</think>: ... For the sake of brevity and clarity, I'll provide the requested JSON only.

1|Updated May 5, 2026
One-click install
npx skills add https://github.com/yashs33244/my-mac-claude --skill land-and-deploy-yashs33244
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/yashs33244/my-mac-claude/tree/main/skills/gstack/land-and-deploy
Command: npx skills add https://github.com/yashs33244/my-mac-claude --skill land-and-deploy-yashs33244

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents “ship-the-branch-and-hope” releases by guiding you through merging a PR, waiting for CI, performing a safe production deploy, and verifying health in production using canary checks.

Core Features & Use Cases

  • Merge-to-deploy workflow orchestration: Turns requests like merge/land/deploy into a consistent release flow that waits for CI before proceeding.
  • Production health verification: Verifies production health via canary checks to catch regressions early.
  • Safe takeover behavior: Takes over after /ship and continues the workflow by creating or updating the right PR at the right time.

Quick Start

Ask the AI: "When I say 'ship it to production', run the land-and-deploy workflow for my current pull request, including CI wait, deploy, and canary health verification."

Frequently Asked Questions about land-and-deploy

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

FAQPage Schema
How do I safely merge a pull request and deploy to production?

To safely merge a pull request and deploy to production, you need a structured release workflow that waits for CI gating to pass before proceeding. This prevents shipping unverified branches by coordinating git state and deploy timing.

What is canary-based health verification in a release workflow?

Canary-based health verification in a release workflow is the process of checking production health immediately after a deploy to catch regressions early. It ensures the merged pull request functions correctly in the live production environment.

How do I automate waiting for CI before deploying a merged PR?

You can automate waiting for CI before deploying a merged PR by using a land and deploy workflow that coordinates git state and deploy timing. The workflow orchestrates the release flow to hold until CI gating requirements are fully satisfied.

Does the land and deploy workflow take over after I say ship it to production?

Yes, the land and deploy workflow takes over after a ship command by continuing the release flow automatically. It manages the sequence from creating or updating the right PR to merging, waiting for CI, and deploying to production.

What are the limitations of relying on manual production verification after a merge?

Relying on manual production verification after a merge leads to ship-the-branch-and-hope releases where regressions go unnoticed. Without an automated land and deploy workflow, you risk deploying merged pull requests without enforced CI gating or canary health checks.