land-and-deploy

Merge pull requests, monitor CI pipelines, and verify production canary health.

Updated May 27, 2026

Search Tags:#production #merge #deploy #ship #ci #canary #pull-request

Ready to run

npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill land-and-deploy-shmurdoc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/Shmurdoc/EasyRide-v1/tree/main/.opencode/skills/gstack-land-and-deploy
Command: npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill land-and-deploy-shmurdoc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual coordination gap between code review completion and production deployment. It automates the risky handoff after a pull request is created, removing the need for developers to manually merge, monitor CI, and verify canary health.

Core Features & Use Cases

Automated PR Merge and CI Wait: Handles merging the pull request and waiting for continuous integration pipelines to pass before proceeding.
Production Canary Verification: Checks production health via canary deployment metrics to ensure the release is stable before confirming success.
Use Case: After running the ship command to create a PR, invoke this skill to hands-off the merge, CI wait, deploy, and verification steps without further intervention.

Quick Start

Use the land-and-deploy skill to merge the current pull request, wait for CI and deploy to complete, and verify production health via 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 automate pull request merge and CI monitoring?▼

Automating pull request merge and CI monitoring is handled by merging the PR and continuously checking CI pipeline status to ensure tests pass before proceeding to deployment.

What is production canary verification in a deployment workflow?▼

Production canary verification checks production health via canary deployment metrics to ensure the release is stable and healthy before confirming deployment success.

How to deploy and verify canary health after a pull request is created?▼

To deploy and verify canary health after creating a PR, invoke the automated workflow to merge the PR, wait for CI pipelines to pass, deploy, and run production canary checks.

Do I need access to git and CI system status to automate deployment verification?▼

Yes, automating deployment verification requires access to git, CI system status, deployment pipelines, and production canary metrics to complete the merge, deploy, and verification cycle.

What is the best way to handle the post-merge deployment workflow hands-off?▼

The best way to handle post-merge deployment hands-off is automating the risky handoff after code review by merging PRs, waiting for CI, and verifying production canary health without manual intervention.