triage

Analyzes GitHub PR review comments, implements accepted fixes, and manages review threads.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/alessioroberto82/claude-plugin-circle --skill triage-alessioroberto82
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/alessioroberto82/claude-plugin-circle/tree/main/plugins/circle/skills/triage
Command: npx skills add https://github.com/alessioroberto82/claude-plugin-circle --skill triage-alessioroberto82

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Handling pull request review feedback is tedious: you must read every comment, judge its validity, implement fixes, reply to reviewers, and resolve threads. This Skill automates that entire loop while keeping you in control of every decision. ## Core Features & Use Cases - Comment Fetching & Parsing: Pulls unresolved review threads from any GitHub PR via GraphQL, or accepts inline pasted comments, and presents them in a structured table. - Verdict Analysis: Reads the actual code around each comment and classifies it as Accept, Reject, or Unclear with a technical rationale, waiting for your approval before changing anything. - Fix Implementation & Publishing Gate: Implements minimal fixes, groups them into conventional commits, and only replies, resolves threads, or pushes after your explicit consent. - Use Case: A reviewer leaves 12 comments on your PR. Run the triage command to get a verdict table, approve the fixes, and have accepted comments resolved with commit references while rejected ones get polite technical rebuttals. ## Quick Start Ask the assistant to triage the review comments on PR #42 and propose fixes for the valid ones.

Frequently Asked Questions about triage

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

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

Run the triage command with a PR number, URL, or pasted inline comments. It fetches unresolved threads via the GitHub GraphQL API, analyzes each against the actual code, and presents an accept/reject/unclear verdict table before making any changes.

How to reply and resolve GitHub review threads in bulk?▼

The Skill batches all thread replies and resolutions into two GraphQL mutation calls using aliases, minimizing API requests. Replies are always posted before resolving so reviewers see the rationale or the fixing commit hash.

Does it push commits or resolve threads without asking?▼

No. A publishing gate requires explicit separate consent before any push, reply, or resolve action. Approving the verdict table or commit plan only authorizes local analysis and commits, never publishing.

Can it triage comments from a different repository?▼

Yes, it accepts cross-repo references like OWNER/REPO#NUMBER. If the target repo differs from your local checkout, it fetches and summarizes the comments read-only but cannot read code or implement fixes.

What happens with unclear or ambiguous review comments?▼

Unclear comments get clarification questions posted to their threads, which stay open and unresolved. Re-running triage after the reviewer responds re-evaluates the thread with full context.