skills.rest
vatsal2210
vatsal2210COMMUNITY
Explore all skills by this author →
Website𝕏@vatsal_n_shahGitHub

pr-triage

Fetch and categorize GitHub pull request review comments into actionable categories.

Updated Apr 12, 2026
Search Tags:#github#triage#code-review#copilot#pull-request#gh-cli#review-comments
One-click install
npx skills add https://github.com/vatsal2210/claude-skills --skill pr-triage-vatsal2210
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-triage
Source: https://github.com/vatsal2210/claude-skills/tree/main/pr-triage
Command: npx skills add https://github.com/vatsal2210/claude-skills --skill pr-triage-vatsal2210

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide a concise, actionable triage of GitHub pull request review comments so authors know exactly what to fix, what to skip, and what needs discussion before merge.

Core Features & Use Cases

  • Fetches all three PR comment types (issue comments, inline review comments, and batched review objects) and consolidates them into a single report.
  • Categorizes each comment as Bug, Legitimate Improvement, By-design Skip, or Needs Discussion, and for actionable items supplies concrete fixes and effort estimates.
  • Drafts polite reply text for by-design threads and surfaces CI status, reviewer identities, and file:line context to prioritize fixes.
  • Use Cases: prepping replies and fixes before addressing feedback, batching review work, and deciding a safe merge order.

Quick Start

Use pr-triage on the PR URL to fetch review comments, categorize them, estimate effort, and produce a ready-to-use triage report.

Frequently Asked Questions about pr-triage

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

FAQPage Schema
How do I triage GitHub pull request review comments efficiently?▼

Triage GitHub pull request review comments by fetching issue comments, inline reviews, and batched objects to categorize feedback into bugs, improvements, skips, or discussions. This generates a consolidated report with effort estimates and draft replies.

Can I categorize PR feedback into actionable items with file:line context?▼

Yes, you can categorize PR feedback by fetching review comments with file:line context. Comments are classified as bugs, legitimate improvements, by-design skips, or needing discussion, providing concrete fixes and effort estimates for actionable items.

Does triaging pull request comments require authenticated GitHub CLI access?▼

Yes, triaging pull request comments requires authenticated access via gh CLI or an MCP. This authentication is necessary to fetch issue comments, review comments, reviewer identities, pagination, and CI status for the PR URL.

What is the best way to prepare replies for skipped GitHub review threads?▼

The best way to prepare replies for skipped threads is to use automated triage that drafts polite reply text for by-design comments. It surfaces reviewer identities and file:line context to help prioritize fixes and decide a safe merge order.

How do I estimate effort for fixing code review comments on a pull request?▼

Estimate effort for fixing code review comments by consolidating all PR feedback into a single triage report. The system categorizes actionable items and supplies concrete effort estimates to help batch review work and prep fixes.

Related Skills

Explore More Software Engineering Skills→
d3mingd3ming

gh-address-comments

Fetch and organize GitHub pull request review comments via gh CLI.

Community
Intermediate
hvent90hvent90
1

fetch-pr-comments

Fetch unresolved PR review threads and pending reviews as JSON.

Community
Advanced
netresearchnetresearch
51

git-workflow

Standardize Git branching, commit conventions, and PR workflows across teams.

Official
Advanced
lucidashlucidash
5

resolve-review

Classify GitHub PR review comments by priority and propose code changes.

Community
Advanced