land-and-deploy

Coordinate PR merge, CI verification, and canary deployment in Bash.

1|Updated Feb 25, 2026

Search Tags:#automation #release #merge #pr #deploy #ci #canary

Ready to run

npx skills add https://github.com/alexandervashurin/semaphore --skill land-and-deploy

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end flow of merging a PR, waiting for CI, triggering deployment, and validating production health via canary checks.

Core Features & Use Cases

End-to-end PR merge orchestration with pre-merge checks and safety gates.
Deploy verification: canary health checks post-deploy, with rollback recommendations.
Post-ship hand-off: hands off to post-ship monitoring and operations.

Quick Start

Invoke /land-and-deploy to start the automated merge, CI wait, and canary deploy verification workflow.

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 verification, and deployment in one workflow?▼

You can automate the entire flow by orchestrating PR merge, CI status checks, and canary deployment verification in a reproducible Bash-based workflow, ensuring production readiness after a PR is merged.

What is canary deployment verification and how does it ensure production readiness?▼

Canary deployment verification performs post-deploy health checks to validate production stability. It assesses application health after shipping and provides rollback recommendations if issues are detected during the canary phase.

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

Yes, GitHub CLI access is required. The automated workflow depends on GitHub CLI to manage PR merges, execute pre-merge safety checks, and monitor CI status checks before triggering canary deployments.

What's the best way to handle post-ship monitoring and operations after a canary deploy?▼

The automated workflow includes a post-ship hand-off feature that transitions deployment responsibilities to post-ship monitoring and operations, ensuring continuous health assessments after the canary deployment is verified.

Can I apply ship and land workflows across multiple projects with automated pre-merge checks?▼

Yes, you can apply ship and land workflows across multiple projects. The automation applies pre-merge checks, deploy verification, and post-deploy health assessments consistently using a reproducible Bash-based flow.

When should I use automated rollback recommendations during canary deployment?▼

Automated rollback recommendations are triggered when canary health checks detect post-deploy issues. This safety gate mechanism ensures production readiness by flagging failures immediately after the PR merge and deploy process.