resolve-review-threads

Triage and resolve unresolved pull request review threads with disposition-based replies.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pull requests accumulate unresolved review threads from bots like Copilot, teammates, and self-review, and handling them ad hoc leads to missed feedback, false fixes, and replies posted under the owner's name that should never have been sent. This Skill enforces a disciplined triage-then-act workflow so every thread gets a disposition before any code changes. ## Core Features & Use Cases - Full thread triage: Fetches every unresolved review thread via the GitHub GraphQL API, distinguishes bot authors from human reviewers using __typename, and assigns each thread a disposition of fix, decline (with reproduction-grade evidence), or route (filed as an idea) before touching any code. - Human-vs-bot safeguards: Fixes and bot threads are replied to and resolved in-thread, while declines or routes on a person's thread are drafted and parked for the owner to send via h9k review resolve, never posted autonomously. - Structured reporting: Emits one THREAD DISPOSITION: block per thread plus a SUMMARY: line, and parks disputed threads with RESOLUTION: disputed and DISAGREEMENT: blocks containing a proposed reply. - Use Case: A follow-up run on a Hall9k-dispatched PR finds six unresolved Copilot threads and two from a teammate; the skill fixes the three valid findings, declines two false claims with scratch-repo evidence, routes one out-of-scope suggestion, and drafts parked replies for the human threads. ## Quick Start Ask the agent to resolve all unresolved review threads on the current branch's open pull request using the resolve-review-threads skill.

Frequently Asked Questions about resolve-review-threads

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

FAQPage Schema
How do I resolve all unresolved review threads on a GitHub pull request?

Fetch unresolved threads with the GitHub GraphQL reviewThreads query, triage each into fix, decline, or route before changing code, then reply in-thread and resolve per disposition. The skill uses gh api graphql for thread data and the resolveReviewThread mutation to close threads.

How to tell bot review comments from human reviewers on GitHub?

Query the comment author's __typename field via GraphQL: it returns Bot for app accounts like Copilot and User for people. This is the provider's own classification, more reliable than guessing from the login string.

Can an agent reply to a human reviewer's comment automatically?

Fix replies can be posted in anyone's thread, but declines or routes on a human-opened thread are never posted autonomously. They are drafted and parked so the owner can send, edit, or drop them via h9k review resolve.

Why does replying to a pull request review comment return a 404?

The REST reply endpoint requires the numeric databaseId of a comment, not the GraphQL node id (PRRC_...). Sending a node id to the REST endpoint 404s; fetch both ids in the initial GraphQL query and use each with its matching API.

What evidence is needed to decline a review suggestion?

A decline requires reproduction-grade evidence: a scratch-repo demonstration showing actual behavior, or a pointer to the code path that already handles the concern. Disagreement alone does not qualify as a decline.