land-and-deploy

Automate PR promotion with merge, canary deployment, and health validation.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/pistosmin/base-one --skill land-and-deploy-pistosmin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/pistosmin/base-one/tree/main/.claude/skills/gstack/land-and-deploy
Command: npx skills add https://github.com/pistosmin/base-one --skill land-and-deploy-pistosmin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the risky process of promoting code from PR to production by coordinating pre-merge checks, deployment canaries, and post-deploy health verifications to minimize outages and rollbacks.

Core Features & Use Cases

  • Pre-merge readiness gate with CI and merge-conflict checks.
  • Auto-merge and canary-based deployment with health checks and rollback options.
  • Deployment strategy detection across common platforms and environments to tailor verification steps.

Quick Start

Trigger the land-and-deploy workflow to automatically merge the PR, promote canaries, 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 production deployment safely?▼

Automating PR merge and production deployment safely requires validating CI success and merge conflicts before auto-merging, then running canary checks and post-deploy health verifications with rollback options to prevent outages.

What is canary-based deployment and how does it verify production health?▼

Canary-based deployment promotes code incrementally while running health checks to validate production stability, automatically triggering a rollback if issues arise during the post-deploy verification phase.

How do I detect deployment platforms and tailor CI-CD verification steps?▼

Detecting deployment platforms involves identifying the target environment to tailor verification steps, ensuring the CI-CD workflow applies the correct canary checks and health validations for that specific platform.

Does this workflow support automatic rollback if production health checks fail?▼

Automatic rollback is supported if production health checks fail during canary verification, providing configurable guardrails and deployment workflows to revert changes and minimize outages.

What pre-merge readiness checks are needed to prevent deployment failures?▼

Pre-merge readiness checks require validating CI success and confirming no merge conflicts exist, acting as a gate to ensure PR readiness before promoting code to production environments.