land-and-deploy

Merge PRs, wait for CI, deploy, and verify production via canary checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Land and deploy workflow automates the end-to-end release process: it merges the PR, waits for CI, deploys, and verifies production health via canary checks. This reduces manual handoffs and the risk of post-merge failures by coordinating checks and deployment steps in a deterministic sequence.

Core Features & Use Cases

  • End-to-end release orchestration: merge, wait for CI, deploy, and canary verification from a single command after a PR is ready.
  • Production health verification: canary checks ensure deployments meet readiness criteria before completion.
  • Reuse with the /ship lifecycle: picks up where /ship leaves off, handling post-merge deployment verification automatically.

Quick Start

Run the land-and-deploy skill to automatically merge the PR, wait for CI, trigger deployment, and verify production health via canary checks.

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 wait, and deployment in a single workflow?

You can automate the end-to-end release process by running a workflow that merges the PR, waits for CI to pass, triggers deployment, and verifies production health via canary checks. This coordinates manual handoffs into a deterministic sequence.

What is canary-based production verification for deployments?

Canary-based production verification checks whether a deployment meets readiness criteria before the release is considered complete. It ensures production health by running canary checks automatically after the deployment step finishes.

How do I verify production health after merging a PR?

To verify production health after merging a PR, you can use an automated deployment workflow that runs canary checks. This ensures deployments meet readiness criteria before completion, reducing the risk of post-merge failures.

Can I use this deployment automation for PRs that are ready to land?

Yes, this workflow applies to PRs that are ready to land and require deployment to production with health checks. It coordinates PR state, CI results, deployment steps, and canary verification automatically.

Does the land-and-deploy workflow work with the /ship lifecycle?

Yes, the land-and-deploy workflow picks up where the /ship lifecycle leaves off, handling post-merge deployment verification automatically. It merges the PR, waits for CI, triggers deployment, and runs canary checks.

What are the limitations of automating merge and deploy workflows?

This workflow is designed for PRs ready to land and deploy to production with health checks. It does not apply to PRs still under review or deployments that do not require canary-based production verification.