lrh-land

Automate end-to-end pull request landing with review, fix, and merge workflows.

1|Updated Apr 7, 2026

Search Tags:#automation #workflow #code review #pull request #github #merge

Ready to run

npx skills add https://github.com/xenotaur/logical_robotics_harness --skill lrh-land

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lrh-land
Source: https://github.com/xenotaur/logical_robotics_harness/tree/main/.claude/skills/lrh-land
Command: npx skills add https://github.com/xenotaur/logical_robotics_harness --skill lrh-land

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates the manual overhead and inconsistency of managing pull request merges by enforcing a rigorous, evidence-backed lifecycle that ensures every PR is reviewed, fixed, and authorized before landing.

Core Features & Use Cases

Automated Lifecycle Chaining: Orchestrates the entire PR flow from review response and fix confirmation to the final merge gate and closeout.
Decision-Based Guardrails: Uses explicit algorithmic rules to handle PR state, record keeping, and merge authorization, preventing human error.
Use Case: Use this skill to safely land a complex PR that requires multiple rounds of review and fix verification, ensuring all project control-plane records are updated and the merge is performed with verified SHA-locked commands.

Quick Start

Use the lrh-land skill to drive the pull request at the provided URL through the complete terminal lifecycle chain.

Frequently Asked Questions about lrh-land

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

FAQPage Schema

How do I automate the pull request merge process on GitHub?▼

To automate pull request merge processes, this Skill chains review-response, fix-confirmation, and merge-gate workflows together. It enforces a rigorous lifecycle that ensures every PR is reviewed, fixed, and authorized before landing.

What is the best way to ensure evidence-backed pull request landing?▼

Evidence-backed pull request landing requires strict adherence to project control-plane records and SHA-locked merge execution. This Skill automates that by applying deterministic state assessment and structured closeout documentation for every merged PR.

How does automated fix confirmation work for pull requests?▼

Automated fix confirmation works by chaining review responses with explicit algorithmic rules that verify PR state. This prevents human error by using decision-based guardrails to authorize merges only after fixes are confirmed.

Can I use this for complex PRs requiring multiple rounds of code review?▼

Yes, you can use this for complex PRs requiring multiple rounds of code review. It safely lands complex PRs by orchestrating the complete flow from review response to final merge gate, ensuring all control-plane records are updated.

Why use SHA-locked merge execution for GitHub workflow automation?▼

SHA-locked merge execution is used to guarantee deterministic state assessment and prevent unauthorized changes during the merge process. It ensures the exact reviewed code is landed using verified commands and structured closeout documentation.