triage-reviews

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pull request reviews accumulate comments from bots and humans across multiple places, and manually verifying each finding against the real code is slow and error-prone. This Skill automates the full triage loop: gathering every comment, validating each finding, fixing valid issues, and closing out review threads. ## Core Features & Use Cases - Complete Comment Gathering: Fetches reviews, inline comments, and issue-level comments via the GitHub CLI with pagination, then 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 findings as valid or false positive. - Fix, Reply, and Resolve: Fixes valid findings, runs lint and 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 a dozen automated review comments, run this Skill to verify each one, push fixes for the real bugs, and produce a summary table showing every verdict and thread status. ## 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 GitHub PR review comments automatically?▼

Fetch all reviews, inline comments, and issue comments with the GitHub CLI, verify each finding against the actual code, fix valid issues, then reply and resolve threads. This Skill automates that entire workflow end to end.

How to resolve GitHub review threads via API?▼

GitHub review threads can only be resolved through the GraphQL API using the resolveReviewThread mutation with the thread's node ID. The REST API has no endpoint for resolving threads, so you must fetch thread IDs via a GraphQL query first.

Can I reply to a specific inline PR review comment?▼

Yes, use the REST endpoint POST /repos/{owner}/{repo}/pulls/{pr}/comments/{comment_id}/replies with the comment's database ID. Note this differs from the GraphQL thread node ID used for resolving.

Does this handle comments from Copilot and Greptile reviewers?▼

Yes, it fetches comments from all sources including Copilot, Greptile, and human reviewers, then deduplicates findings grouped by file and line. Summary-level comments like Greptile's overview are left untouched.

What happens to valid findings that cannot be fixed automatically?▼

Valid but unfixed findings are reported in the final summary table and their review threads are deliberately left open. This keeps the real bug visible in the PR view until a maintainer files a follow-up.