land-and-deploy

Merge PRs, wait for CI, validate canary deployments, and promote to production.

Updated Mar 21, 2026

Search Tags:#github #merge #pr #deploy #ci #canary

Ready to run

npx skills add https://github.com/TimHL5/carousel --skill land-and-deploy-timhl5

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/TimHL5/carousel/tree/main/.claude/skills/gstack/land-and-deploy
Command: npx skills add https://github.com/TimHL5/carousel --skill land-and-deploy-timhl5

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Land and deploy automates the end-to-end process of merging a PR, waiting for CI, validating production canary health, and promoting changes to production. This reduces manual handoffs and accelerates safe releases.

Core Features & Use Cases

Auto-merge: Merges the PR after CI succeeds, respecting repo rules.
CI & Merge Gatekeeping: Waits for required checks to complete and handles merge conflicts.
Canary & Production Verification: Runs canaries and health checks before production rollout, with optional production URL verification.
Revert & Rollback: Offers safe revert options if deployment issues arise, including canary rollbacks.
Post-merge Deploy Strategy: Detects platform and deploy workflows to verify deployment paths for different environments (staging/production).

Quick Start

Automatically merge a PR, wait for CI to pass, run canaries, and promote to production once healthy.

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 merging a GitHub PR and deploying it after CI passes?▼

To automate merging a GitHub PR and deploying after CI, you need a workflow that merges PRs, waits for required checks to complete, and validates canary health before promoting to production.

How does canary deployment verification work before promoting to production?▼

Canary deployment verification runs health checks and canaries before production rollout, optionally verifying production URLs. It ensures changes are healthy before full production promotion and offers rollbacks if issues arise.

Do I need GitHub CLI to automate PR merge and deploy workflows?▼

Yes, automating the end-to-end land-and-deploy workflow requires the GitHub CLI and access to the repository. It also needs a deploy configuration in CLAUDE.md or autodetected platform details to guide verification.

What happens if CI checks fail or merge conflicts occur during automated deployment?▼

During automated deployment, the system handles merge conflicts and waits for required CI checks to complete as part of its merge gatekeeping. If deployment issues arise, it offers safe revert and rollback options.

Can I automatically revert a production deployment if canary health checks fail?▼

Yes, if canary health checks fail or deployment issues arise, the workflow offers safe revert options including canary rollbacks. This ensures production stability when promoting changes.