land-and-deploy

Merge a PR after CI passes and verify production health via canary checks.

1|Updated Mar 1, 2026

Search Tags:#deployment #deploy #ci #canary #pull-request #land

Ready to run

npx skills add https://github.com/anishs1207/agentic-cli --skill land-and-deploy-anishs1207

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/anishs1207/agentic-cli/tree/main/.agents/skills/gstack-land-and-deploy
Command: npx skills add https://github.com/anishs1207/agentic-cli --skill land-and-deploy-anishs1207

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Land and deploy workflow. Merges the PR, waits for CI and deploy, verifies production health via canary checks. Takes over after /ship creates the PR. Use when: "merge", "land", "deploy", "merge and verify", "land it", "ship it to production".

Core Features & Use Cases

Automatic PR landing: Merges the ready-to-ship PR after CI passes.
Canary-based health checks: Verifies production health before full rollout.
Rollback-ready: Offers revert options on failures and failed deployments.
End-to-end release orchestration: Coordinates preflight checks, merge, deploy, and validation across platforms.

Quick Start

Invoke this skill with /land-and-deploy to automatically merge the PR, trigger the canary deployment, 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 merging a pull request and deploying it to production?▼

You can automate the PR merge and production deployment flow using an orchestration tool that merges the pull request, waits for CI, and triggers the deploy automatically. This skill coordinates that entire sequence with preflight checks and platform detection.

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

A canary deployment is a release strategy that routes a portion of traffic to the new version to verify production health before a full rollout. This skill performs canary-based health checks after merging and deploying your PR to ensure stability across environments.

Do I need the GitHub CLI to merge and deploy pull requests automatically?▼

Yes, the GitHub CLI is required to merge and deploy pull requests automatically. The skill uses GitHub CLI and repository access to perform preflight checks, merge the PR, and trigger the subsequent CI and deployment pipeline.

Can I rollback a failed production deployment after merging a pull request?▼

Yes, you can rollback a failed production deployment after merging a pull request. This skill is rollback-ready and offers revert options when failures or degraded health are detected during the canary verification checks.

What are the limitations of automating PR merges and canary deployments?▼

Limitations of automating PR merges and canary deployments include the strict requirement for pre-configured deployment and canary verification steps. This skill depends on a configured environment with GitHub CLI access and cannot validate production health without deterministic steps already in place.