land-and-deploy

Automate PR merging, CI waiting, production deployment, and canary health checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Land-and-deploy automates the land-and-deploy workflow: merging PRs, waiting for CI, deploying to production, and verifying health with canary checks.

Core Features & Use Cases

  • Auto-detects PR from the current branch, merges after CI success
  • Deploys to production and runs canary health checks
  • Handles edge cases such as missing PR, failed CI, or failed canary health

Quick Start

Merge the PR by running land-and-deploy and monitor the deployment health.

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, waiting for CI, and deploying to production?

Automate the land-and-deploy workflow by merging PRs, waiting for CI success, deploying to production, and verifying health with canary checks. It operates as a mostly automated sequence with safety gates to stop for authentication, PR state, CI failures, and canary health.

What happens if CI fails or canary health checks fail during an automated deploy?

The automated deploy sequence stops at safety gates when CI fails or canary health checks fail. It handles edge cases such as missing PR, failed CI, or failed canary health by halting the workflow to prevent bad code from reaching production.

Do I need the GitHub CLI to merge PRs and run canary deployments automatically?

Yes, you need GitHub CLI access to run the land-and-deploy workflow. The Skill requires GitHub CLI to auto-detect PRs from the current branch, merge them after CI success, and execute the subsequent production deployment steps.

How does a canary release health check work after merging a PR?

Canary health checks verify production health after deployment by running automated safety gates. The workflow tracks canary health and logs telemetry and plan outputs, stopping automatically if verification fails to ensure deployment confidence.

Can I use this automated PR merge and deploy workflow for any Git branch?

The workflow operates on PR-based flows and auto-detects the PR from the current branch. It expects a SKILL.md frontmatter and optional scripts/references/assets directories, running as an automated sequence with safety gates for PR state and authentication.