triage-reviews

Fetch GitHub PR review comments, verify findings against code, fix valid issues, and resolve threads.

Updated Aug 29, 2026
One-click install
npx skills add https://github.com/larscolombia/lubot-hunter-mcp-2026 --skill triage-reviews-larscolombia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage-reviews
Source: https://github.com/larscolombia/lubot-hunter-mcp-2026/tree/main/.agents/skills/triage-reviews
Command: npx skills add https://github.com/larscolombia/lubot-hunter-mcp-2026 --skill triage-reviews-larscolombia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing PR feedback from multiple bots and human reviewers is tedious: comments are scattered across reviews, inline threads, and issue comments, some findings are false positives, and threads stay unresolved even after fixes ship. This Skill automates the full triage loop from gathering comments to pushing fixes and resolving threads. ## Core Features & Use Cases - Comment Aggregation: Fetches all review comments via the GitHub API (reviews, inline comments, and issue comments) and deduplicates findings across Copilot, Greptile, and human reviewers. - Evidence-Based Verification: Reads the actual code at each referenced file and line, cross-checks with documentation lookups and web search, and classifies each finding as Valid or False positive. - Fix, Reply, and Resolve: Fixes valid findings, runs lint/tests, commits and pushes, then replies on each review thread and resolves it via GraphQL only when the finding is fixed or a false positive. - Use Case: After opening a PR that attracted a dozen automated review comments, run this Skill to verify each one against the real code, fix the three genuine bugs, dismiss the false positives with evidence, and leave a clean, fully-resolved PR. ## Quick Start Triage all review comments on PR 42, fix the valid findings, and resolve the addressed threads.

Frequently Asked Questions about triage-reviews

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

FAQPage Schema
How do I triage PR review comments automatically?▼

Fetch all comments via the GitHub API (reviews, inline comments, and issue comments), verify each finding against the actual code at the referenced file and line, fix valid issues, then reply and resolve threads. This Skill automates that entire loop.

How to resolve GitHub review threads from the command line?▼

GitHub review threads can only be resolved via the GraphQL API, not REST. Use gh api graphql with the resolveReviewThread mutation and the thread's node ID, which you fetch by querying reviewThreads on the pull request.

How do I handle false positives from Copilot or Greptile reviews?▼

Read the actual code at the referenced location before accepting any finding. If the reviewer misread the code or referenced outdated behavior, reply on the thread with concrete evidence such as the file and line showing the correct behavior, then resolve it.

Does this work with the GitHub CLI and Graphite?▼

Yes, the workflow uses the gh CLI for all GitHub API calls and pushes changes with gt submit when using Graphite, falling back to a standard git push otherwise. A GitHub repository with an open PR is required.

When should a review thread be left unresolved?▼

Leave a thread open when the finding is valid but cannot be fixed in the current pass, such as when lint or test failures block the fix. Resolving it would hide a real bug, so the thread stays open for a follow-up.