land-and-deploy

Merge pull requests, deploy code changes, and verify production readiness.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Santiagoisper/BOPE_VERSION_DEFINITIVA --skill land-and-deploy-santiagoisper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/Santiagoisper/BOPE_VERSION_DEFINITIVA/tree/main/.agents/skills/gstack/land-and-deploy
Command: npx skills add https://github.com/Santiagoisper/BOPE_VERSION_DEFINITIVA --skill land-and-deploy-santiagoisper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of merging pull requests, deploying changes, and verifying the production environment, reducing manual steps and minimizing risk.

Core Features & Use Cases

  • PR Merge and Deploy: Automatically merge PRs, trigger deployment, and monitor the process.
  • Production Verification: Conduct canary checks to ensure production health after deployment.
  • Use Case: After the /ship command creates a pull request, use this Skill to ensure the code is merged, deployed, and production is healthy.

Quick Start

To initiate the merge, deployment, and verification process for the current branch, use the command /land-and-deploy.

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 merging and deployment in my CI/CD workflow?

Automate PR merging and deployment by triggering the workflow after a pull request is created, which automatically merges the code, deploys changes, and monitors the process to reduce manual steps and minimize risk.

What is production verification after a deployment?

Production verification is conducting canary checks to ensure production health after deployment, confirming that the newly deployed code changes are stable and the environment is running as expected.

Do I need GitHub API integration to automate pull request handling?

Yes, GitHub API integration is required for pull request handling, and CI/CD platform access is also required for deployment to fully automate the merge, deploy, and verification process.

Can I use an automated workflow to merge pull requests and trigger deployment together?

Yes, you can use an automated workflow to merge pull requests and trigger deployment together, streamlining the process of deploying code changes and verifying production readiness in one step.

What's the best way to verify production health after deploying code changes?

The best way to verify production health after deploying code changes is to conduct canary checks, ensuring the environment is stable and healthy after the automated deployment process completes.

When should I not use automated deployment workflows for pull requests?

You should not use automated deployment workflows when manual oversight is required for complex merges, or when your CI/CD platform access or GitHub API integration is not properly configured for pull request handling.