land-and-deploy

Merge a PR, wait for CI, deploy, and verify production canary health.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/ComputerConnection/zach-pack --skill land-and-deploy-computerconnection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/ComputerConnection/zach-pack/tree/main/skills/gstack-land-and-deploy
Command: npx skills add https://github.com/ComputerConnection/zach-pack --skill land-and-deploy-computerconnection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Land-and-deploy automates the end-to-end flow of merging a PR, waiting for CI, deploying to production, and verifying health via canary checks. It reduces manual handoffs and mitigates risk by gating production releases on successful CI and live Canary health.

Core Features & Use Cases

  • Auto-detects the PR associated with the current branch, merges it when ready, and triggers the deployment pipeline.
  • Waits for CI to complete and monitors production health via canary checks before signaling completion.
  • Provides a structured workflow for post-ship deployment, rollbacks, and verification in production environments.

Quick Start

Run /land-and-deploy to automatically merge the PR, wait for CI, deploy, 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 merging a GitHub pull request and deploying to production?

You can automate merging a pull request and deploying to production by running the /land-and-deploy command, which auto-detects the PR, merges it, triggers the deployment pipeline, and monitors production health via canary checks.

What is a canary check in a CI/CD deployment workflow?

A canary check in a CI/CD deployment workflow is a validation step that monitors production health after a release. It gates the completion of a deployment on live canary success to mitigate risk before signaling completion.

Does this deployment automation work with GitHub-based CI/CD pipelines?

Yes, this deployment automation is designed for GitHub-based workflows where CI must pass and canaries must succeed before completion. It supports auto-detection of PRs and waits for CI to finish before triggering deployment.

How do I wait for CI to pass before triggering a production release?

To wait for CI to pass before triggering a production release, the workflow monitors CI status after merging a PR. It gates the deployment pipeline on successful CI completion and then proceeds to validate production health.

Can I roll back a production deployment if canary verification fails?

Yes, you can roll back a production deployment if canary verification fails. The workflow provides a structured process for post-ship deployment, rollbacks, and verification with configurable fallbacks in production environments.