land-and-deploy

Merge pull requests and verify production deployment health with canary checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual friction and cognitive load associated with the final stages of the software delivery lifecycle, ensuring that code merges, deployments, and production verification are handled consistently and safely.

Core Features & Use Cases

  • Automated Deployment Pipeline: Orchestrates the merge of pull requests and triggers downstream CI/CD deployment processes.
  • Production Health Verification: Performs automated canary checks to ensure the new deployment is stable and healthy.
  • Use Case: After finalizing a feature, use this Skill to land the PR, wait for the deployment to complete, and verify that the production environment remains stable without manual intervention.

Quick Start

Invoke the land-and-deploy skill to merge the current pull request and verify the production deployment 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 automate pull request merges and production deployments?

Automated canary health checks monitor the production environment after a deployment to ensure stability. This Skill performs post-merge validation automatically, verifying that newly deployed code remains healthy without requiring manual intervention.

What is the best way to verify production health after a CI/CD deployment?

Automated canary health checks monitor the production environment after a deployment to ensure stability. This Skill performs post-merge validation automatically, verifying that newly deployed code remains healthy without requiring manual intervention.

Do I need git integration to automate continuous delivery pipelines?

Yes, git integration is required to execute the automated landing sequence. Access to CI/CD deployment triggers is also necessary to orchestrate the pull request merges and verify the subsequent production deployments.

Can I use this for continuous delivery pipelines requiring automated canary checks?

Yes, this applies to continuous delivery pipelines requiring automated canary health checks and post-merge validation. It orchestrates the entire workflow from pulling the request to verifying the production environment remains stable.

Why does manual deployment verification cause friction in software delivery?

Manual deployment verification creates cognitive load and inconsistency during the final stages of the software delivery lifecycle. Automating the merge, deployment, and canary health checks ensures code lands consistently and safely.