land-and-deploy

Merge pull requests, deploy code to production, and perform canary checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Read, Write, Glob, AskUserQuestion, and includes scripts (resource) components.

What problem does it solve?

Streamlines the process of merging Pull Requests (PRs), conducting continuous integration (CI), deploying changes, and verifying production health, reducing manual steps and potential errors.

Core Features & Use Cases

  • Automated Workflow: Automates the complete PR lifecycle, from merge to deployment and verification.
  • CI/CD Integration: Integrates with CI tools for smooth code testing and integration.
  • Production Health Checks: Performs canary checks to ensure the changes do not negatively impact production.
  • Use Case: Ideal for developers and DevOps engineers looking to automate the deployment of PRs to production environments, ensuring that only stable code is released.

Quick Start

Use the land-and-deploy skill after /ship creates a PR to automatically merge, deploy, and verify the changes.

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 PR merge, CI, and deployment to production?

Automating PR merge, CI, and deployment requires a workflow tool that merges Pull Requests, runs continuous integration, deploys code, and performs canary checks to verify production health, reducing manual steps and potential errors.

What is a canary release check in deployment automation?

A canary release check in deployment automation is a production health verification step performed after deploying changes. It ensures that newly released code does not negatively impact the production environment by monitoring specific health indicators before full rollout.

How do I integrate CI/CD pipelines with PR workflow automation?

CI/CD pipeline integration with PR workflow automation connects continuous integration tools directly to the PR lifecycle. This ensures smooth code testing and integration happens automatically during the merge and deployment process.

Does deployment automation work with Bash and standard shell scripts?

Yes, PR deployment automation works with Bash and standard shell scripts. The workflow requires Bash, Read, Write, Glob, and AskUserQuestion tools to orchestrate the merge, continuous integration, deployment, and production health verification process.

What is the best way to verify production health after a canary release?

The best way to verify production health after a canary release is to perform automated canary checks immediately following the deployment. This verifies that changes do not negatively impact production before completing the full rollout.

When should I not use automated PR deployment for production releases?

You should not use automated PR deployment for production releases when manual oversight is required for compliance, or when your project lacks proper CI testing infrastructure to support reliable canary checks before changes impact production.