land-and-deploy

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

1|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/rkumar261/studio-cast --skill land-and-deploy-rkumar261
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/rkumar261/studio-cast/tree/main/.claude/skills/gstack/land-and-deploy
Command: npx skills add https://github.com/rkumar261/studio-cast --skill land-and-deploy-rkumar261

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Land and deploy workflow for PRs: merges the PR, waits for CI, deploys to production, and verifies health via canary checks.

Core Features & Use Cases

  • End-to-end automation of PR land after CI checks, including canary verification.
  • Supports release workflows where a PR is merged, deployed, and production health is validated before final rollout.
  • Use Case: After a critical bug fix, run land-and-deploy to merge the PR, wait for CI, deploy to production, and confirm canary health automatically.

Quick Start

Provide a PR context and let the skill merge after CI, 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, production deployment, and canary health verification in one workflow?▼

To automate PR land and deploy, this skill merges your PR, waits for CI completion, deploys to production, and verifies health via canary checks using Bash-based automation.

What is a canary deployment check and when do I need it in a release workflow?▼

A canary check validates production stability after deploying a merged PR. You need it in release workflows where production health must be confirmed before final rollout to catch issues early.

Can I use Bash automation to wait for CI checks before merging a pull request?▼

Yes, you can use Bash-based automation to wait for CI checks before merging a pull request. This skill coordinates the CI wait, ensuring the PR merges only after CI completes successfully before production deployment.

Does this deployment workflow require any external dependencies or tooling?▼

No external dependencies are required. The skill operates independently using Bash-based automation and allowed tooling to coordinate the merge, CI wait, deployment, and canary health checks.

What's the best way to verify production health after deploying a critical bug fix?▼

The best way to verify production health after deploying a critical bug fix is running canary checks. This skill automates merging the PR, waiting for CI, deploying to production, and confirming canary health.

When should I not use an automated land and deploy workflow for production releases?▼

Avoid automated land and deploy workflows when you need manual control over deployment timing, custom rollback procedures, or when canary health checks are not supported in your production environment.