land-and-deploy

Merge PRs, await CI, deploy to production, and run canary health checks.

1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/cheng80/rummipoker --skill land-and-deploy-cheng80
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/cheng80/rummipoker/tree/main/.agents/skills/gstack-land-and-deploy
Command: npx skills add https://github.com/cheng80/rummipoker --skill land-and-deploy-cheng80

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Land and deploy workflow. Merges the PR, waits for CI and deploys to production, and validates production health via canary checks. It takes over after /ship creates the PR. Use when you need to merge, land, deploy, or verify production quickly and safely.

Core Features & Use Cases

  • End-to-end deployment orchestration: merges PRs, triggers CI, deploys to production, and monitors canary health.
  • Production health verification: canary checks catch issues before full rollout and reduce risk.
  • Post-ship handoff: coordinates with /ship workflows to finalize deployment.

Quick Start

Invoke land-and-deploy to merge the PR, wait for CI, deploy to production, and verify canary health.

Frequently Asked Questions about land-and-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is an automated PR merge and deploy workflow?

An automated PR merge and deploy workflow merges a pull request, waits for CI to pass, deploys to production, and runs canary health checks to validate the rollout safely.

How do I merge a pull request, wait for CI, and deploy to production automatically?

You can orchestrate the end-to-end PR promotion by invoking the land-and-deploy process, which automatically merges the PR, awaits CI completion, deploys, and verifies production health.

Does automated deployment support canary health checks for production rollouts?

Yes, the deployment orchestration includes canary health checks that monitor production health after deployment, catching potential issues early to reduce release risk before full rollout.

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

The best way to verify production health after merging a PR is to use an automated workflow that deploys to production and runs canary checks to ensure stability before completing the rollout.

When should I not use automated PR promotion for deployment?

You should not use automated PR promotion if your project lacks integration with PR workflows, CI pipelines, deployment targets, or canary verification systems, as these are required for safe orchestration.