land-and-deploy

Merge PRs, wait for CI, and verify canary health in production.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Scivor/helm --skill land-and-deploy-scivor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/Scivor/helm/tree/main/skills/gstack/land-and-deploy
Command: npx skills add https://github.com/Scivor/helm --skill land-and-deploy-scivor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Land and deploy workflow automates merging a PR, waiting for CI, and verifying production health through canary checks. It takes over after /ship creates the PR to streamline the release flow.

Core Features & Use Cases

  • Auto-merge PRs once CI passes.
  • Deploy to production with canary health verification and rollback if needed.
  • Handoff and governance: supports integration points for /ship initiated releases.

Quick Start

Trigger land-and-deploy on a ready PR and watch it orchestrate merge, CI wait, and production deployment.

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 verification, and canary deployment end to end?

Automating PR merge, CI verification, and canary deployment is handled by orchestrating Git operations, waiting for CI checks to pass, and verifying production health before completing the release.

What is a canary deployment workflow with automated CI checks?

A canary deployment workflow with automated CI checks merges a PR, waits for CI to pass, routes a portion of production traffic to the new version, and verifies health metrics before full rollout.

How do I auto-merge a GitHub PR only after CI passes?

Auto-merging a GitHub PR after CI passes requires a workflow that coordinates Git operations with CI/CD triggers, enforces safety checks on CI status, and then executes the merge automatically.

Can I roll back a canary deployment if production health checks fail?

Rolling back a canary deployment when health checks fail is supported by the workflow, which verifies canary health in production and triggers a rollback if needed.

Does automated canary deployment work with GitHub-based release workflows?

Automated canary deployment is designed specifically for GitHub-based release workflows where automated merge, CI verification, and canary deployment reduce cycle time.

When should I not use automated canary deployment for my PRs?

Automated canary deployment may not suit workflows lacking CI/CD triggers or production health metrics, since the automation relies on verifying canary health and safety checks before completing a release.