land

Coordinates PR landing with QA validation for non-deployment merges using Nexus workflow hub.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Nexus PR landing workflow reduces the risk and manual effort of merging shipped PRs when deployment is not expected. It ensures a clear, governed handoff and consistent post-merge validation.

Core Features & Use Cases

  • Enforces a safe merge path when a project has no production deploy surface.
  • Guides governance checks and QA validation for merged PRs in CLI, library, desktop apps, or docs-only changes.
  • Provides a repeatable quick-start flow to land PRs with confidence.

Quick Start

Run the land command after a PR is ready to merge to complete the landing workflow.

Frequently Asked Questions about land

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I land a PR when there is no production deployment surface?▼

To land a PR without a production deployment surface, this Skill coordinates the merge process by enforcing governance checks, QA validation, and a safe merge path using the Nexus workflow hub. It ensures a governed handoff for merged changes.

What is the best way to manage governance and QA validation for a merged PR?▼

Managing governance and QA validation for a merged PR requires a structured workflow. This Skill guides you through the necessary checks and validations to reduce manual effort and ensure a safe merge path after merge readiness is achieved.

How do I safely merge CLI or library code changes without a deployment step?▼

Safely merging CLI or library code changes without a deployment step is supported by this Skill. It applies a repeatable landing workflow that handles post-merge validation and governance for non-deployable projects.

Can I use this workflow for docs-only changes in a repository?▼

Yes, you can use this workflow for docs-only changes in a repository. The Skill is designed to handle any project with no production deploy surface, including desktop apps and documentation, by enforcing a safe merge path.

How do I start the PR landing process after merge readiness?▼

To start the PR landing process after merge readiness, run the land command. This initiates the Nexus landing workflow to complete the necessary governance checks and post-merge validation.