land-and-deploy

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Land and deploy orchestration automates the end-to-end release flow: merging the PR, waiting for CI, canary checks, and production promotion.

Core Features & Use Cases

  • End-to-end release automation: merge, land, and ship to production with validated production health.
  • Canary health verification: perform health checks before promoting features live.
  • Production handoff: coordinate PR closure, deployment, and post-deploy checks in a single workflow.

Quick Start

Run the land-and-deploy skill after a PR is merged to trigger CI wait, canary checks, and production promotion.

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 PR, waiting for CI, and deploying to production?

You can automate this end-to-end release flow by running a land-and-deploy workflow that merges the PR, waits for CI completion, and deploys to production. This orchestration handles the entire release sequence with a single command.

What is a canary health check in a production deployment workflow?

A canary health check verifies production stability before fully promoting a new feature. In a land-and-deploy workflow, the system performs these health checks after merging the PR and waiting for CI, ensuring the deployment is safe before final promotion.

Can I use automated release orchestration for Git-based projects that require PR handoffs after merge?

Yes, automated release orchestration applies to Git-based projects requiring end-to-end release coordination. It manages PR closure, CI verification, and production deployment with canary checks in a single workflow.

How do I ship to production with one command after a PR is merged?

To ship to production with one command, trigger the land-and-deploy workflow after your PR is merged. The system will automatically wait for CI, execute canary health checks, and promote the release to production.

Does automated land and deploy orchestration support waiting for CI before promoting features live?

Yes, land and deploy orchestration supports waiting for CI. The workflow merges the PR, pauses to wait for CI completion, and then performs canary health checks before promoting features to the live production environment.

What are the limitations of automating PR merges and canary deployments in a single workflow?

Automating PR merges and canary deployments in a single workflow is limited to Git-based projects. It requires end-to-end release orchestration and depends on successful CI completion and canary health verification before proceeding to production promotion.