land-and-deploy

Automates PR merge, CI wait, deployment and canary health checks for safe production rollout.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/jeisenback/original-curse-killer --skill land-and-deploy-jeisenback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/jeisenback/original-curse-killer/tree/main/.claude/skills/land-and-deploy
Command: npx skills add https://github.com/jeisenback/original-curse-killer --skill land-and-deploy-jeisenback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merges PRs after they pass CI, triggers deployment workflows, and validates production health via canaries, reducing manual toil and risk in post-merge releases.

Core Features & Use Cases

  • Automates the end-to-end flow from merge readiness to production verification, including pre-merge checks, CI waiting, and canary health checks.
  • Supports merging PRs auto or manually based on repository rules, triggering deployment pipelines and health validation.
  • Use case: After a PR is ready, run land-and-deploy to ensure a safe production rollout with canary monitoring and quick revert if issues are detected.

Quick Start

Type /land-and-deploy to automatically merge the PR, wait for CI, deploy to production, and run canary health 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 PR merge, CI checks, and production deployment in one step?

Automating PR merge, CI checks, and production deployment requires a tool that enforces pre-merge gates and monitors CI. This Skill handles the end-to-end flow, triggering deployment workflows and validating production health via canaries after merge.

What is a canary check in production health verification?

A canary check in production health verification validates production readiness after deployment. This Skill runs canary health checks to monitor the newly deployed production environment, enabling quick revert if issues are detected during the rollout.

How do I wait for CI to pass before merging a pull request?

Waiting for CI to pass before merging a pull request is handled by monitoring CI status as a pre-merge gate. This Skill enforces these gates, ensuring the PR merge auto or manually only happens after CI validation is complete.

Does this deployment automation work with projects where ship creates PRs?

This deployment automation is designed specifically for projects where /ship creates PRs. It integrates into that workflow to automate the subsequent merge, CI wait, deployment, and production health verification processes.

What happens if a canary health check fails after a production rollout?

If a canary health check fails after a production rollout, the Skill is designed to reduce risk by identifying the issue. It validates production readiness and supports quick revert if issues are detected during canary monitoring.