land-and-deploy

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end release workflow from PR merge through production verification, reducing risk and manual toil during deployments.

Core Features & Use Cases

  • End-to-end release automation: merge PR, wait for CI, deploy, and verify health via canaries.
  • Production verification: canary checks guard against regressions before full rollout.
  • Handover after ship: takes over deployment validation and promotion once the PR is ready.

Quick Start

Run land-and-deploy to merge the PR from the current branch, wait for CI, deploy canary, and verify production 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 PR merge and deployment with canary health checks?

Automating PR merge and deployment with canary checks is done by coordinating the end-to-end release workflow, waiting for CI, deploying canaries, and verifying production health. This reduces manual toil and ensures safe promotion.

What is a canary deployment workflow and when do I need it?

A canary deployment workflow is a release engineering process that guards against regressions by validating production health before full rollout. You need it when releasing software that requires reduced risk and auditable steps.

Can I use this release workflow for teams that require auditable deployment steps?

Yes, this release workflow applies to teams releasing software that require reduced risk, auditable steps, and reliable post-merge health validation. It manages the handoff after ship to ensure safe promotion to production.

What's the best way to verify production health after merging a PR?

Verifying production health after merging a PR is best handled by automating the end-to-end release workflow, which integrates CI wait periods and canary checks to validate post-merge health before full promotion.

Does this deployment automation wait for CI before rolling out to production?

Yes, this deployment automation waits for CI completion after merging the PR from the current branch. It then deploys the canary and verifies production health before proceeding with the full rollout.

Why does my release workflow need a handoff after ship to production?

Your release workflow needs a handoff after ship because the automation takes over deployment validation and promotion once the PR is ready. This ensures production health checks are reliably completed without manual intervention.