skills.rest
hetsheth-droid
hetsheth-droidCOMMUNITY
Explore all skills by this author →
GitHub

land-and-deploy

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

Updated Mar 31, 2026
Search Tags:#deployment#release#merge#ci#canary#land-and-deploy
One-click install
npx skills add https://github.com/hetsheth-droid/toolbox-template --skill land-and-deploy-hetsheth-droid
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/hetsheth-droid/toolbox-template/tree/main/incubating/gstack/land-and-deploy
Command: npx skills add https://github.com/hetsheth-droid/toolbox-template --skill land-and-deploy-hetsheth-droid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merges the PR, waits for CI, deploys to production, and verifies health via canaries, reducing manual toil and risk in releases.

Core Features & Use Cases

  • Orchestrates post-ship release workflows, including merging the PR, awaiting CI, triggering deployment, and canary health checks.
  • Enforces gates to ensure production readiness before completion, minimizing rollback risk.
  • Use Case: when a PR is ready to ship, run /ship to create the PR and then /land-and-deploy to finish the release with automated verification.

Quick Start

Run /land-and-deploy to merge the PR, 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
How do I automate PR merge, CI wait, and production deployment in one step?▼

Canary health verification checks production stability after deploying by monitoring the canary-based rollout policy. It enforces gates before completion to ensure production readiness, reducing manual toil and minimizing rollback risk during releases.

What's the best way to safely merge and deploy a release with canary checks?▼

You need access to the repository, PR, CI system, and deployment environments. The automated release workflow requires these connections to merge the PR, wait for CI, deploy to production, and adhere to the canary-based rollout policy.

How does canary health verification work after a production deployment?▼

You can automate the end-to-end release by merging a PR, waiting for CI, deploying to production, and verifying canary health automatically. This orchestrates post-merge release workflows with enforced gates to ensure production readiness and minimize rollback risk.

Do I need specific repository or CI system access to run automated deployments?▼

The best way to safely merge and deploy is using an automated release workflow that merges the PR, waits for CI, triggers deployment, and performs canary health checks. This enforces production readiness gates and minimizes rollback risk.

Related Skills

Explore More Software Engineering Skills→
diiviikk5diiviikk5

land-and-deploy

Merge PRs, wait for CI, deploy to production, and validate health via canary checks.

Community
Advanced
avav25avav25
2

deploy-to-production

Automate production deployments with health checks and rollback procedures.

Community
Advanced
tropekstropeks

land-and-deploy

Coordinate PR merge, CI checks, production deployment, and canary verification.

Community
Advanced
a29paula29paul
1

land-and-deploy

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

Community
Advanced