walk-pr-review-findings

Walk pr-review findings with the owner and post approved GitHub reviews.

Updated Aug 16, 2026
One-click install
npx skills add https://github.com/Hallmanac/hall9k --skill walk-pr-review-findings-hallmanac
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: walk-pr-review-findings
Source: https://github.com/Hallmanac/hall9k/tree/main/.claude/skills/walk-pr-review-findings
Command: npx skills add https://github.com/Hallmanac/hall9k --skill walk-pr-review-findings-hallmanac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? A Hall9k pr-review task reviews someone else's pull request read-only and parks its findings report as NeedsHuman, leaving the owner to decide what actually gets posted. This Skill walks that report (or a mention follow-up's addendum) finding by finding with the owner and posts only what they explicitly approve under their own GitHub login. ## Core Features & Use Cases - Finding-by-finding walkthrough: Presents adversarial and conformance findings in the report's own order and collects a per-finding directive: dismiss, handle personally, or post on the owner's behalf. - Batched GitHub review posting: Accumulates approved line-anchored comments and submits them as one formal review (COMMENT, REQUEST_CHANGES, or APPROVE) via a single gh api call, only after showing the exact draft and receiving an explicit go. - Mention reply handling: Answers tagged comments by posting the owner-approved drafted reply into the exact thread it came from, using the REST in_reply_to id when the mention was an inline review-comment reply. - Use Case: An auto-pr-review task parked NeedsHuman with review-1-findings.md for owner/repo#42. You run this Skill to review each finding with the owner, batch three approved comments into a REQUEST_CHANGES review, post one conversational remark separately, and close the task with h9k review resolve --merge-ready. ## Quick Start Ask the agent to walk the findings report of the parked pr-review task and post only the comments you approve to the pull request.

Frequently Asked Questions about walk-pr-review-findings

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

FAQPage Schema
How do I post a batched GitHub pull request review with line comments?

Collect every approved line-anchored comment into one JSON payload with path, line, side, and body fields, then submit it with gh api repos/OWNER/REPO/pulls/NUMBER/reviews using event COMMENT, REQUEST_CHANGES, or APPROVE. This lands the review and all comments atomically as one formal submission.

How do I reply to a specific review comment thread on GitHub?

Use gh api repos/OWNER/REPO/pulls/NUMBER/comments with the in_reply_to field set to the numeric reply id of the comment. Do not pass the GraphQL node id (PRRC_...) to in_reply_to, since the REST endpoint rejects it with a 404.

What is a Hall9k pr-review task and when does it park NeedsHuman?

A pr-review task reviews someone else's pull request read-only and produces a findings report, then parks NeedsHuman because posting anything requires the owner's explicit decision. It is created with h9k task add --type pr-review --from-pr or minted automatically by auto-pr-review.

Can the review event be inferred from finding severity automatically?

No. The review event (comment, request changes, or approve) must always be named explicitly by the owner and is never inferred from how severe the findings are. Nothing is submitted without the owner approving the exact draft first.

Why does h9k review resolve reject --needs-fixes on a pr-review task?

A pr-review task has no diff of its own, so there is nothing for a fix session to apply. The only accepted verdict is --merge-ready, which parks the task AwaitingAuthor until the pull request merges or closes.