skills.rest
akiyoshi
akiyoshiCOMMUNITY
Explore all skills by this author →
GitHub

land-and-deploy

Automate PR merge, deployment, and production health verification workflows.

Updated Apr 11, 2026
Search Tags:#merge#pr#deploy#ci#canary#health-check#land-and-deploy
One-click install
npx skills add https://github.com/akiyoshi/gstack-copilot-jp --skill land-and-deploy-akiyoshi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/akiyoshi/gstack-copilot-jp/tree/main/.github/skills/land-and-deploy
Command: npx skills add https://github.com/akiyoshi/gstack-copilot-jp --skill land-and-deploy-akiyoshi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the end-to-end land, deploy, and production verification workflow for PRs, reducing risk and manual toil by coordinating pre-merge gates, merge, deployment, and health validation.

Core Features & Use Cases

  • Pre-merge readiness gate checks (CI status, mergeability, drift detection) before merging.
  • Automated land-and-deploy pipeline that merges, deploys, and validates production health, including canary when available.
  • Comprehensive readiness reporting and guardrails for safe merge flow with configurable merge strategies.

Quick Start

Run the /land-and-deploy command on a PR that's ready for production to start the merge, deploy, and health verification sequence.

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 deploy to production with health checks?▼

Automating PR merge and deploy requires a pipeline that merges, deploys, and validates production health. This workflow coordinates pre-merge gates, deployment, and health checks to ensure safe production releases.

What is a pre-merge readiness gate for CI and deploy pipelines?▼

A pre-merge readiness gate checks CI status, mergeability, and drift detection before merging. It acts as a guardrail to ensure only safe, validated PRs proceed to the deploy and health verification stages.

How do I verify production health after deploying a merged PR?▼

Verifying production health after deploying a merged PR involves running automated health checks across common platforms. The workflow validates production health, including canary checks when available, to confirm release stability.

Do I need GitHub CLI authentication to automate PR land and deploy?▼

Yes, GitHub CLI authentication is required to automate PR land and deploy. Enforcing authentication ensures secure access for merging PRs and coordinating the subsequent deployment and health verification sequence.

Can I use configurable merge strategies for safe production releases?▼

Configurable merge strategies are supported for safe production releases. The workflow coordinates merge methods with pre-merge gates and readiness reporting, ensuring reliable land-and-deploy practices across common platforms.

What's the best way to handle canary deployments during a PR merge?▼

Handling canary deployments during a PR merge involves an automated land-and-deploy pipeline that validates production health, including canary when available. This coordinates merge, deploy, and health verification for reliable releases.

Related Skills

Explore More Software Engineering Skills→
chicago-joechicago-joe

babysit

Monitor GitHub pull request checks, reviews, and CI status for merge readiness.

Community
Intermediate
rkumar261rkumar261
1

land-and-deploy

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

Community
Advanced
samm-the-devsamm-the-dev

pr-check

Monitor CI checks and triage review comments on pull requests.

Community
Advanced
a29paula29paul
1

land-and-deploy

Merge approved PRs, wait for CI and deployment pipelines, and verify production canary checks.

Community
Advanced