land-and-deploy

Automate merging PRs, waiting for CI, deploying optionally with health checks.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/LaPaGaYo/nexus --skill land-and-deploy-lapagayo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-and-deploy
Source: https://github.com/LaPaGaYo/nexus/tree/main/skills/support/land-and-deploy
Command: npx skills add https://github.com/LaPaGaYo/nexus --skill land-and-deploy-lapagayo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Land and deploy automates the post-merge workflow: merging the PR, waiting for CI, optionally deploying, and validating production health when deployment is chosen.

Core Features & Use Cases

  • Merges the PR after readiness checks
  • Waits for CI to complete and reports status
  • Optionally deploys to production and runs health checks
  • Handles handoff metadata after ship readiness and PR handoff

Quick Start

Trigger land-and-deploy after a PR is merged and ready for production verification.

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 PR, waiting for CI, and deploying to production?

Automating the land-and-deploy workflow merges PRs after readiness checks, waits for CI to complete, optionally deploys to production, and verifies production health. It coordinates merge, deployment, and health checks using PR metadata, CI status, and Nexus state.

What is the best way to verify production health after deploying a merged PR?

Verifying production health after deploying a merged PR is handled by running automated health checks post-deployment. The workflow coordinates with Nexus state and CI status to ensure the correct execution path and provide visibility into production health.

When do I need to use a land and deploy workflow for CI and PR management?

You need a land and deploy workflow when a PR is ship-ready and requires post-merge automation. It applies after ship-ready PR handoff to coordinate merging, waiting for CI completion, and optional production deployment with health validation.

Can I skip deployment and only merge a PR while waiting for CI status?

Deployment is optional within the land-and-deploy workflow. You can merge a PR and wait for CI status reporting without deploying, as the workflow handles handoff metadata and coordinates execution paths based on whether production deployment is requested.

Does the land and deploy workflow coordinate with Nexus state and CI status?

The land and deploy workflow coordinates with PR metadata, CI status, and Nexus state to ensure correct execution path and visibility. It uses these data sources to manage merge, land, and optional deployment operations while validating production health.

Why does production health verification fail after a canary deploy workflow?

Production health verification coordinates with Nexus state and CI status to validate deployment outcomes. If health checks fail, the workflow ensures visibility into the execution path, though specific failure recovery steps depend on the handoff metadata and deployment configuration.