lrh-confirm-fixes

Correlate GitHub review threads with the current HEAD diff to verify pull request fixes.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/xenotaur/logical_robotics_harness --skill lrh-confirm-fixes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lrh-confirm-fixes
Source: https://github.com/xenotaur/logical_robotics_harness/tree/main/.claude/skills/lrh-confirm-fixes
Command: npx skills add https://github.com/xenotaur/logical_robotics_harness --skill lrh-confirm-fixes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates the uncertainty of the pre-merge phase by independently verifying that pushed code fixes actually resolve reviewer comments, preventing premature merges and surfacing unresolved issues.

Core Features & Use Cases

  • Independent Verification: Validates fixes against the live HEAD diff rather than relying on potentially outdated execution records.
  • Thread Resolution: Automatically resolves threads that are clearly satisfied by the diff while surfacing ambiguous or problematic findings for human review.
  • Merge-Readiness Verdict: Provides a definitive green-light status and a safe merge one-liner only after CI and automated reviewer checks have passed on the final commit.

Quick Start

Run the lrh-confirm-fixes skill by providing the URL of the pull request you wish to verify.

Frequently Asked Questions about lrh-confirm-fixes

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

FAQPage Schema
How do I verify pull request fixes before merging to GitHub?

To verify pull request fixes before merging, the skill correlates GitHub review threads with the current HEAD diff to independently confirm that pushed code changes resolve reviewer comments and ensure merge-readiness.

What is automated thread resolution for code review workflows?

Automated thread resolution is the process of matching GitHub review comments against the live HEAD diff, automatically closing threads that are clearly satisfied by the code changes while flagging ambiguous or problematic findings for human review.

How do I check merge-readiness status for a GitHub pull request?

To check merge-readiness status, the skill aggregates CI status and automated reviewer checks on the final commit, providing a definitive green-light verdict and a safe merge one-liner only after all checks have passed.

Can I validate code review fixes against the current HEAD diff instead of execution records?

Yes, independent verification validates fixes directly against the live HEAD diff rather than relying on potentially outdated execution records, ensuring the actual pushed code resolves the reviewer comments.

Does this pre-merge verification process require any external dependencies?

No external dependencies are required to run this pre-merge verification process. You simply provide the URL of the pull request you wish to verify, and it correlates the review threads with the diff.

Why should I use independent verification instead of manually checking review threads?

Independent verification eliminates the uncertainty of the pre-merge phase by surfacing unresolved issues and preventing premature merges, providing a definitive merge-readiness verdict that manual checking might miss.