lrh-closeout

Automate post-merge closeout for Logical Robotics Harness sessions.

1|Updated Apr 7, 2026

Search Tags:#automation #workflow #devops #governance #closeout #lrh

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates the manual overhead of finalizing development sessions by automating the synchronization of execution records, work items, workstreams, and design proposals after a pull request is merged.

Core Features & Use Cases

Automated State Transition: Updates execution records to landed status and resolves work items in a single, validated workflow.
Artifact Integrity: Ensures all project artifacts are moved to their correct buckets and linked with proper provenance.
Human-in-the-loop Safety: Provides a comprehensive closeout plan and requires explicit confirmation before any file system changes occur.

Quick Start

Run the lrh-closeout skill by providing the URL of the merged pull request to automatically finalize all associated work items and execution records.

Frequently Asked Questions about lrh-closeout

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

FAQPage Schema

How do I automate work item synchronization after a pull request is merged?▼

Automating work item synchronization after a merged pull request requires validating artifact states and resolving session transcripts across the project control plane. Providing the merged pull request URL triggers an automated workflow that updates execution records to landed status.

What is the best way to finalize development sessions without manual overhead?▼

Finalizing development sessions without manual overhead involves automating the synchronization of execution records, work items, workstreams, and design proposals. This ensures consistent state across the project control plane following pull request merges.

How does human-in-the-loop validation work for file system modifications during closeout?▼

Human-in-the-loop validation for file system modifications works by generating a comprehensive closeout plan that requires explicit confirmation before any changes occur. This ensures artifact integrity and provenance while preventing unauthorized state transitions.

Can I use this automated closeout workflow for project maintenance tasks at scale?▼

Using this automated closeout workflow for project maintenance tasks at scale is supported through validated state transitions across execution records, work items, and workstreams. The workflow applies governance rules to ensure consistent artifact landing and provenance linking.

Why does closeout require validation of artifact states before resolving session transcripts?▼

Closeout requires validation of artifact states before resolving session transcripts to ensure all project artifacts are moved to their correct buckets and linked with proper provenance. This prevents inconsistent state across the project control plane.

What are the limitations of automating LRH session closeout?▼

Limitations of automating LRH session closeout include the requirement for human-gated confirmation of all file system modifications and the dependency on providing a merged pull request URL to initiate the workflow. The process cannot bypass explicit validation steps.