triage-reviews

Fetch, verify, and resolve GitHub PR review comments against actual code.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? PR review feedback arrives scattered across multiple comment types (reviews, inline comments, issue comments) from bots and humans, and manually verifying each finding against the real code is slow and error-prone. This Skill automates the full triage loop: gathering comments, verifying findings, fixing valid issues, and resolving threads. ## Core Features & Use Cases - Comprehensive Comment Gathering: Fetches all review comments via the GitHub API across reviews, inline comments, and issue comments, then deduplicates findings from 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 findings 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 the GitHub GraphQL API. - Use Case: After opening a PR that received 15 review comments from automated reviewers, run this Skill to verify each one, fix the 4 real bugs, dismiss the false positives with evidence, and produce a summary table of every verdict. ## Quick Start Ask the assistant to triage the review comments on PR number 42, verify each finding against the code, fix the valid ones, 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 across the reviews, comments, and issues endpoints, then verify each finding against the actual code at the referenced file and line. Classify each as Valid or False positive, fix valid issues, and reply on each thread with the verdict.

How to resolve GitHub review threads with the API?▼

GitHub review threads can only be resolved via the GraphQL API using the resolveReviewThread mutation with the thread's node ID. Fetch thread IDs with a paginated GraphQL query on reviewThreads, since the REST API has no resolve endpoint.

Does this work with automated reviewers like Copilot and Greptile?▼

Yes, the workflow fetches comments from all sources and deduplicates findings across Copilot, Greptile, and human reviewers by grouping them by file and line. Each finding is still verified against the real code before being accepted or rejected.

What happens when a valid finding cannot be fixed automatically?▼

The finding is reported as Valid (unfixed) in the final summary table, and its review thread is left open rather than resolved. This keeps the real bug visible in the PR view so maintainers can track it in a follow-up.

Why does the REST API fail to resolve review threads?▼

GitHub's REST API provides no endpoint for resolving review threads; resolution is only exposed through GraphQL. The thread ID used for resolution is a GraphQL node ID, which differs from the REST comment database ID.