land-and-deploy

Merges pull requests and verifies production canary health after CI/CD deployment completes.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Jia-Hong-Peng/jolike.com --skill land-and-deploy-jia-hong-peng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/Jia-Hong-Peng/jolike.com/tree/main/.claude/skills/gstack/land-and-deploy
Command: npx skills add https://github.com/Jia-Hong-Peng/jolike.com --skill land-and-deploy-jia-hong-peng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merging a pull request and verifying that the deployment is healthy in production currently requires manual coordination between Git, CI/CD pipelines, and monitoring tools. This Skill automates the entire landing workflow so engineers can ship code with confidence without context switching.

Core Features & Use Cases

  • Automated PR Merge: Merges the pull request and triggers the CI/CD pipeline without manual git commands.
  • Deploy Verification: Waits for the deployment to finish and runs canary checks to confirm production health.
  • Use Case: After creating a PR with /ship, use this Skill to land the changes and verify they are live in production without opening multiple tabs or running manual health checks.

Quick Start

Use the land-and-deploy skill to merge the current pull request and verify that production is healthy after the deployment completes.

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 verifying production health?▼

Automating pull request merges and verifying production health involves triggering a CI/CD pipeline after a merge and running canary checks to confirm deployment stability without manual intervention.

Can I verify production deployment health automatically after merging a PR?▼

Yes, production deployment verification can be automated by waiting for the CI/CD pipeline to finish and running canary health checks to confirm the new code is live and stable.

What is the best way to land code changes without manual Git commands?▼

The best way to land code changes is automating the end-to-end merge-deploy-verify cycle, integrating Git hosting platforms and CI systems to merge pull requests and verify production automatically.

Do I need a CI/CD pipeline to automate PR merges and canary checks?▼

Yes, integrating with Git hosting platforms, CI/CD pipelines, and production canary health checks is required to complete the automated merge, deploy, and verification cycle without manual intervention.

How does an automated canary check work after a production deployment?▼

Automated canary checks wait for the CI/CD deployment to finish and then execute health checks against production to confirm the merged pull request changes are operating correctly without manual monitoring.

Are there limitations to automating the end-to-end merge and deploy workflow?▼

Automating the merge and deploy workflow requires existing integration with Git hosting platforms, CI systems, and production canary health checks, making it unsuitable for environments lacking these CI/CD components.