land-and-deploy

Merges pull requests, waits for CI and deploy, and verifies production health via canary checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a pull request is created, teams still need to merge it safely, wait for CI and deployment pipelines to finish, and confirm production is healthy. This Skill automates that final stretch of the release workflow so nothing ships unverified. ## Core Features & Use Cases - PR Merge and Landing: Merges the pull request created by the /ship workflow and coordinates the landing process. - CI and Deploy Monitoring: Waits for continuous integration and deployment pipelines to complete before proceeding. - Production Verification: Runs canary checks to confirm production health after the deploy finishes. - Use Case: After /ship opens a PR for a new feature, invoke this Skill to merge it, watch the deploy pipeline, and verify the live service responds correctly before declaring the release done. ## Quick Start Ask the agent to land the PR and deploy it to production, verifying health with 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 merge a PR and deploy to production automatically?

Invoke the land-and-deploy workflow after your PR is created. It merges the pull request, waits for CI and deployment pipelines to finish, then runs canary checks against production to confirm the release is healthy.

What is the difference between ship and land-and-deploy workflows?

The ship workflow creates the pull request, while land-and-deploy takes over afterward to merge it, monitor CI and deployment, and verify production health. They are sequential stages of one release pipeline.

Can land-and-deploy run in headless or CI environments?

Yes, the workflow detects headless sessions via its preamble and blocks on interactive prompts rather than failing silently. In spawned sessions it auto-selects recommended options and reports results as prose.

What happens if the deploy fails or canary checks detect problems?

The workflow verifies production health through canary checks after deployment completes. If verification fails, the release is not confirmed healthy and the issue surfaces for investigation before the workflow reports success.

Does land-and-deploy require the gstack toolchain installed?

Yes, it depends on gstack binaries under ~/.claude/skills/gstack/bin for configuration, telemetry, and session detection. These are installed by running the repository setup script for your coding-agent host.