skills.rest
curielmc
curielmcCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

land-and-deploy

Merge PRs, deploy after CI, and validate production health with canaries.

Updated Feb 27, 2026
Search Tags:#ci-cd#canary#release-engineering#production-verification#pr-merge#land-and-deploy
One-click install
npx skills add https://github.com/curielmc/beat-SPY --skill land-and-deploy-curielmc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/curielmc/beat-SPY/tree/main/.claude/skills/gstack/land-and-deploy
Command: npx skills add https://github.com/curielmc/beat-SPY --skill land-and-deploy-curielmc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Land and deploy automates end-to-end production release by merging PRs, waiting for CI, deploying, and validating production health with canaries.

Core Features & Use Cases

  • Merges PRs and drives the deployment pipeline after CI completes.
  • Verifies production health via canaries and automatic promotion.
  • Takes over after /ship and handles edge cases like merge conflicts or failed deploys.

Quick Start

Type /land-and-deploy to start the end-to-end merge, deploy, and canary 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 merging pull requests and deploying to production after CI passes?▼

Canary deployment in release engineering verifies production health by routing a subset of traffic to the new version, checking metrics, and automatically promoting or rolling back based on validation results.

What is the best way to handle merge conflicts or failed deploys during automated production releases?▼

Release guardrails for PR deployments are pre-merge readiness checks, post-deploy canary health checks, and rollback options that ensure safe handoff and prevent unhealthy code from reaching production.

How do I start an end-to-end merge, deploy, and canary verification workflow?▼

Canary health checks validate production health by monitoring deployed application metrics and automatically promoting the release if checks pass, or initiating a rollback if failures are detected.

Do I need feature branches and a passing CI pipeline to use automated release orchestration?▼

Yes, automated release orchestration applies to workflows that begin with a PR on feature branches and require CI to pass before promoting to production, ensuring pre-merge readiness is satisfied.

Related Skills

Explore More Software Engineering Skills→
mvillmowmvillmow
18

verify-pr-ready

Verify GitHub pull requests for CI checks, approvals, and merge conflicts.

Community
Basic
mr-daedaliummr-daedalium
107

land-and-deploy

Merge PRs, trigger deployment, and verify canary health in CI/CD pipelines.

Community
Advanced
a29paula29paul
1

land-and-deploy

Merge approved PRs, wait for CI and deployment pipelines, and verify production canary checks.

Community
Advanced
lemiglemig

land-and-deploy

Merge PRs, wait for CI, deploy to production with canary health checks.

Community
Advanced