land-and-deploy

Automate PR merge, CI wait, deployment, and canary health checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Land and deploy workflow. Merges the PR, waits for CI and deploy, verifies production health via canary checks. Takes over after / ship creates the PR. Use when: "merge", "land", "deploy", "merge and verify", "land it", "ship it to production". (gstack)

Core Features & Use Cases

  • Merges PRs, waits for CI, deploys, and canary-prove production health.
  • Takes over after /ship creates the PR and handles post-deploy steps.
  • Use when orchestrating release flows that begin with merge/land/deploy.

Quick Start

Trigger land-and-deploy after a PR merge to start the automated merge, canary deployment, and health-check flow

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 merge and deploy workflows with canary health checks?

Automate merge and deploy workflows by coordinating PR merge, waiting for CI to pass, triggering deployment, and running canary-based production health checks to verify release readiness end-to-end.

What does a canary deployment check do after a PR merge?

A canary deployment check verifies production health after a PR merge by monitoring a partial release, ensuring the new code is stable before completing the full deployment pipeline.

How do I wait for CI to pass before deploying a PR to production?

Wait for CI to pass before deploying by orchestrating a release pipeline that monitors build status after a PR merge, automatically proceeding to deployment only when CI checks succeed.

Can I use this to ship changes to production after creating a PR?

Yes, you can ship changes to production after a PR is created. The workflow takes over post-PR creation, handling the merge, CI wait, deployment, and canary health verification automatically.

Does this workflow support Bash scripting for deterministic deployment pipelines?

Yes, the workflow satisfies deterministic scripting via Bash, providing structured guidance through frontmatter metadata to ensure reliable and repeatable merge, deploy, and canary check execution.

What are the limitations of automating land and deploy sequences?

The land and deploy automation is designed for release pipelines triggered by merge, land, deploy, or ship sequences, and depends on CI passing and canary checks succeeding before completing production deployment.