land-and-deploy

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

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/adamtpang/summon.company --skill land-and-deploy-adamtpang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/adamtpang/summon.company/tree/main/.claude/skills/land-and-deploy
Command: npx skills add https://github.com/adamtpang/summon.company --skill land-and-deploy-adamtpang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a pull request is created, engineers still need to manually merge it, watch CI pipelines, wait for deployment, and confirm production is healthy. This Skill automates that final stretch of the shipping workflow so code lands safely without manual babysitting. ## Core Features & Use Cases - Automated PR Merge: Merges the pull request created by the /ship workflow and monitors the process end to end. - CI and Deploy Monitoring: Waits for CI checks and deployment pipelines to complete before declaring success. - Production Verification: Runs canary checks against production to confirm the deploy is healthy. - Use Case: After running /ship to open a PR, say "land it" and the Skill merges the PR, watches CI and deploy, then verifies production health with canary checks before reporting completion. ## Quick Start Ask the assistant to merge and deploy the current pull request 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 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 to finish, then runs canary checks against production to confirm the release is healthy.

What happens after the /ship command creates a pull request?

The land-and-deploy skill takes over after /ship creates the PR. It handles merging, monitors CI and deploy pipelines, and verifies production health so you do not need to watch the process manually.

Does land-and-deploy verify production after deployment?

Yes, it runs canary checks against production after the deploy completes. This confirms the new release is healthy before the workflow reports success.

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

Yes, the preamble detects session kind including headless and spawned sessions. In headless mode it blocks on decisions requiring user input, while spawned sessions auto-choose recommended options and report results as prose.

When should I not use an automated merge-and-deploy workflow?

Avoid it when the PR has unresolved review feedback, failing CI checks, or when the release requires manual coordination such as database migrations or staged rollouts that need human judgment at each step.