land-and-deploy

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

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/aicodepro/ai-agent-nexi --skill land-and-deploy-aicodepro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/aicodepro/ai-agent-nexi/tree/main/agent/skills/gstack/land-and-deploy
Command: npx skills add https://github.com/aicodepro/ai-agent-nexi --skill land-and-deploy-aicodepro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a pull request is created, engineers still face a risky manual sequence: merging at the right time, watching CI, waiting for deploy, and confirming production is healthy. This Skill automates that final stretch of the shipping workflow so merges land safely and production regressions are caught immediately. ## Core Features & Use Cases - Automated PR Merge: Takes over after the /ship skill creates a PR and merges it once conditions are met. - CI and Deploy Monitoring: Waits for CI pipelines and deployment processes to complete before proceeding. - Production Verification: Runs canary checks against production to confirm the deploy is healthy. - Use Case: You just finished a feature and ran /ship to open the PR. Instead of babysitting the merge, invoke this skill to land the PR, watch the deploy roll out, and verify production health with canary checks before you move on. ## Quick Start Ask the assistant to merge the current pull request and deploy it to production, verifying health with canary checks. Note: this skill is part of the gstack skill suite and expects the gstack CLI helpers (gstack-config, gstack-update-check, etc.) installed under ~/.claude/skills/gstack/bin.

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 skill after your PR is created. It merges the pull request, waits for CI and the deploy to finish, then runs canary checks against production to confirm the release is healthy.

What is the difference between /ship and /land-and-deploy in gstack?

The /ship skill 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 steps in the same shipping workflow.

Does land-and-deploy work in headless or CI sessions?

Yes, the skill detects the session kind (interactive, spawned, or headless) via its preamble. In headless sessions it blocks instead of prompting, and in spawned sessions it auto-chooses recommended options without interactive questions.

What happens if AskUserQuestion is unavailable during the deploy workflow?

The skill falls back based on session type: spawned sessions auto-select the recommended option, headless sessions stop with a BLOCKED status, and interactive sessions render the decision as a prose brief and wait for a typed reply.

What are the prerequisites for running the land-and-deploy skill?

You need the gstack CLI helpers installed under ~/.claude/skills/gstack/bin, a git repository with an open pull request (typically created by /ship), and access to the CI and deployment pipeline the skill monitors.