land-and-deploy

Orchestrate PR merge, CI wait, deployment, and canary verification workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Land and deploy workflow orchestration for PRs: merge, wait for CI, deploy to production, and verify Canary health.

Core Features & Use Cases

  • End-to-end coordination of PR merge, CI wait, deployment, and health verification
  • Deterministic execution flow with prompts and gating to ensure safe releases
  • Use case: when a PR is ready, run the land-and-deploy workflow to merge, deploy, and verify canary health before finalizing

Quick Start

Invoke land-and-deploy on a PR to merge, deploy, and verify production health.

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 PR merge, CI wait, and production deployment in one workflow?

Automated PR merge, CI wait, and production deployment are orchestrated end-to-end by coordinating merge, CI pipeline monitoring, deployment, and canary verification with deterministic prompts to ensure repeatable releases.

What is a canary verification step in a land and deploy workflow?

Canary verification in a land and deploy workflow is a production health check executed after deployment to ensure release stability before finalizing, gating the workflow against unhealthy canary states.

Does land and deploy workflow orchestration work with any CI pipeline and Git-based repository?

Land and deploy workflow orchestration applies to Git-based repositories that use pull requests, CI pipelines, and production health checks, coordinating these existing components deterministically.

What's the best way to ensure safe production releases when merging pull requests?

Safe production releases are ensured by applying deterministic execution flow with prompts and gating during PR merge, CI wait, deployment, and canary health verification to prevent unsafe finalization.

How to coordinate CI pipeline gating and canary health checks for a release?

CI pipeline gating and canary health checks are coordinated by orchestrating the end-to-end land-and-deploy workflow, applying deterministic prompts to wait for CI and verify production health before finalizing.

When should I use an end-to-end land and deploy workflow instead of manual deployment?

An end-to-end land and deploy workflow should be used when a PR is ready and you need repeatable, safe releases through automated merge, CI wait, deployment, and canary health verification.