land-and-deploy

Automate GitHub PR merge, CI gating, and canary deployment workflows.

4|2|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/florianhorner/mammamiradio --skill land-and-deploy-florianhorner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/florianhorner/mammamiradio/tree/main/.claude/skills/gstack/land-and-deploy
Command: npx skills add https://github.com/florianhorner/mammamiradio --skill land-and-deploy-florianhorner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Land and Deploy workflow automates the end-to-end lifecycle of a PR: merging, waiting for CI, and deploying with canary health checks to production.

Core Features & Use Cases

  • End-to-end PR lifecycle automation: from merge through land to production deployment with canary validation.
  • CI-driven deployment gating: ensures production health only after CI confirms success.
  • PR handover and post-deploy checks: clear status and rollback plans if canaries fail.

Quick Start

Trigger the land-and-deploy workflow by merging the PR, waiting for CI to pass, and deploying to production with canary checks.

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 and deploy to production with canary checks?

Automating a GitHub PR merge and deploy requires a workflow that merges the PR, waits for CI pipelines to pass, and deploys to production using canary health checks. This ensures CI success before deployment and validates post-deploy health.

What is a CI-gated canary deployment in a PR lifecycle?

A CI-gated canary deployment is an automated workflow that blocks production deployment until continuous integration pipelines confirm success, then releases changes gradually via canaries to verify production health before completing the PR handover.

How can I wait for CI to pass before deploying a merged PR automatically?

You can wait for CI to pass before deploying a merged PR by using an automated land-and-deploy workflow that gates production deployment on CI pipeline success, ensuring only validated changes are released with canary verification.

Does this land and deploy workflow handle rollbacks if the production canary fails?

Yes, the land and deploy workflow includes post-deploy validation and clear rollback plans if canaries fail. It ensures production health is verified during the canary phase before completing the final PR handover.

Can I use this PR lifecycle automation for my GitHub CI pipelines?

Yes, this PR lifecycle automation applies directly to GitHub PR lifecycles and CI pipelines. It automates the end-to-end flow from merging through land to production deployment with canary validation.

What are the limitations of automating deployments with canary verification?

Automating deployments with canary verification depends entirely on CI pipeline success to gate releases. If CI fails, deployment is blocked, and the workflow requires clear rollback plans to handle failed canary health checks during the post-deploy phase.