land-and-deploy

Merge a pull request, wait for CI, deploy, and verify production with canary checks.

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/yahav123147/paid-ads-cro-skills --skill land-and-deploy-yahav123147
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/yahav123147/paid-ads-cro-skills/tree/main/skills/land-and-deploy
Command: npx skills add https://github.com/yahav123147/paid-ads-cro-skills --skill land-and-deploy-yahav123147

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents risky deployments by guiding you through a safe land-and-deploy workflow that only finishes once CI and production health checks pass.

Core Features & Use Cases

  • PR merge and landing flow: Merges the PR and proceeds to verification instead of assuming deployment is safe.
  • CI wait and deploy: Waits for CI results, then triggers the deploy step.
  • Production verification via canary checks: Confirms production stability using canary health checks before concluding.
  • Guided takeover after /ship: Takes over when you initiate shipping with /ship, matching common “merge and verify” team workflows.

Quick Start

Run land-and-deploy when you say merge, land, deploy, merge and verify, land it, ship it to production, and let it coordinate the merge, CI gating, deploy, and canary verification end-to-end.

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 verify production health?

To safely merge a pull request and verify production health, use a coordinated land-and-deploy workflow that merges the PR, waits for CI completion, triggers the deploy, and runs canary checks before finishing.

What is a canary check in a deployment workflow?

A canary check in a deployment workflow is a production verification step that confirms system stability by monitoring health metrics after a deploy, ensuring the new changes do not cause production issues before concluding the ship process.

How do I automate CI gating and deployment after a PR merge?

You can automate CI gating and deployment after a PR merge by running a land-and-deploy workflow that waits for CI results to pass, then automatically triggers the deploy step and verifies production health.

Does the land-and-deploy workflow require any external dependencies or tools?

The land-and-deploy workflow has no external dependencies, relying on allowed tools, repository mode handling, and operational guardrails to execute the merge, deploy, and canary verification steps deterministically.

What is the best way to ship changes to production without causing downtime?

The best way to ship changes to production safely is to use a guided workflow that merges the PR, gates on CI completion, deploys the changes, and verifies production stability with canary checks before finalizing.

When should I not use an automated merge and deploy workflow?

You should not use an automated merge and deploy workflow if your project lacks deterministic execution support or allowed tools for repository mode handling and operational guardrails, which are required to run the workflow correctly.