land-and-deploy

Automates GitHub PR merge, CI wait, deployment, and canary health verification workflows.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/fray-cloud/coin --skill land-and-deploy-fray-cloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/fray-cloud/coin/tree/main/.claude/skills/gstack/land-and-deploy
Command: npx skills add https://github.com/fray-cloud/coin --skill land-and-deploy-fray-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Land-and-deploy automates merging a PR, waiting for CI, performing the deployment, and verifying production health with canary checks. It helps teams reduce manual toil and minimize production risk by coordinating merge, deploy, and validation in a tight, auditable flow.

Core Features & Use Cases

  • End-to-end PR merge, deployment, and health verification after a ship flow.
  • Canary-based production validation with clear rollback options if issues arise.
  • Works with PRs from the current branch or explicit PRs, with optional verification URL for post-deploy checks.

Quick Start

Run /land-and-deploy to merge the PR, wait for CI, deploy to production, 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
What is an automated merge and deploy workflow with canary verification?

An automated merge and deploy workflow merges a GitHub PR, waits for CI checks, deploys to production, and verifies post-deploy health using canary checks to ensure release safety.

How do I automate GitHub PR merge, CI checks, and production deployment in one flow?

You can automate GitHub PR merge, CI checks, and production deployment by running an end-to-end workflow that validates pre-deploy readiness, waits for CI, deploys, and checks post-deploy health signals.

Can I use canary checks to verify production health after deploying a GitHub PR?

Yes, you can use canary checks to verify production health after deploying by providing an optional verification URL, which validates post-deploy health signals before completing the workflow.

Does this deployment workflow support rollback options if post-deploy canary checks fail?

Yes, the deployment workflow provides clear rollback options if issues arise during canary-based production validation, ensuring that failed post-deploy health checks can be safely reversed.

Do I need a specific PR to run an end-to-end merge and deploy workflow?

You do not need a specific PR; the workflow applies to PRs created from the current branch or a specified PR, allowing flexible targeting for the merge, deploy, and verification process.