land-and-deploy

Automate PR merge, CI-wait, deployment, and canary health verification.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merges the PR, waits for CI, deploys to production, and verifies health via canary checks, reducing risk and manual toil in release workflows.

Core Features & Use Cases

  • Auto-detects PR readiness and merges when CI is green.
  • Orchestrates deployment and post-deploy health verification using canaries.
  • Use Case: release automation from PR to production with minimal manual steps and explicit rollback paths.

Quick Start

Invoke the land-and-deploy skill after a PR is prepared for merge to land, 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 PR merge, deployment, and production health verification?

Automating PR merge, deployment, and production health verification requires orchestrating CI-wait, deployment, and canary checks. This skill automates the end-to-end release workflow, detecting PR readiness, merging when CI is green, deploying, and validating production health with configurable rollback paths.

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

Canary deployment verifies production health by routing a subset of traffic to the new release and checking for errors. This skill orchestrates canary checks post-deploy, using configurable thresholds to validate production health and ensure rollback readiness before completing the release.

How do I merge a pull request only after CI checks pass?

Merging a pull request after CI checks pass involves auto-detecting PR readiness and waiting for a green CI status. This skill automates this process by monitoring CI workflows and merging the PR automatically once all checks are successful, reducing manual toil.

Can I configure base branches and rollback thresholds for release orchestration?

Configuring base branches and rollback thresholds for release orchestration is supported. This skill applies to PR workflows across Git repositories and CI setups, allowing configurable thresholds and base branches to ensure safe merges, deployments, and automated rollback readiness.

What is the best way to reduce manual toil in release management workflows?

Reducing manual toil in release management workflows is best achieved through automated release orchestration. This skill handles the end-to-end PR to production pipeline, automatically merging, waiting for CI, deploying, and verifying health via canaries with explicit rollback paths.

When should I use automated canary checks for production validation?

Automated canary checks for production validation should be used when deploying to production requires strict health verification. This skill applies to PR workflows needing a safe merge and deployment, using canaries to validate production health and trigger rollback readiness if thresholds fail.