lrh-review-response

Resolves open pull request review comments with validated, traceable fixes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes references (resource) components.

What problem does it solve?

This skill addresses open pull request review comments by providing a structured, traceable, and validated workflow that ensures every piece of feedback is triaged, addressed, and verified against project standards.

Core Features & Use Cases

  • Traceable Triage: Mints unique prompt IDs for every review session, linking fixes directly to the feedback that prompted them.
  • Canonical Validation: Automatically runs formatting, linting, and test suites to ensure fixes do not introduce regressions.
  • Use Case: When a reviewer leaves multiple comments on a complex feature branch, use this skill to systematically address each point, validate the code, and push the updates with a clear audit trail.

Quick Start

Invoke the lrh-review-response skill by providing the URL of the open pull request you wish to address.

Frequently Asked Questions about lrh-review-response

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

FAQPage Schema
How do I resolve open pull request review comments systematically?

Resolving open pull request review comments systematically involves using a structured triage protocol to address feedback, running local canonical validation scripts to prevent regressions, and maintaining traceability through unique prompt IDs.

How does traceability work for code review fixes on active development branches?

Traceability for code review fixes on active development branches works by minting unique prompt IDs for each review session, linking every code update directly to the specific reviewer feedback that prompted it.

Do I need the GitHub CLI to automate pull request review workflows?

Yes, you need the GitHub CLI to automate pull request review workflows, as it is a required dependency for fetching open comments, operating on active development branches, and maintaining repository integrity.

What's the best way to ensure code review fixes do not introduce regressions?

The best way to ensure code review fixes do not introduce regressions is to execute canonical validation scripts locally, automatically running formatting, linting, and test suites against project-specific guardrails before pushing.

Can I use this structured triage protocol for complex feature branch reviews?

Yes, you can use this structured triage protocol for complex feature branch reviews to systematically address multiple reviewer comments, validate code against project standards, and ensure design-context continuity.