review-pr

Fetch and assess GitHub PR review comments for the current branch.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/hpark0011/mirror --skill review-pr-hpark0011
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/hpark0011/mirror/tree/main/.agents/skills/review-pr
Command: npx skills add https://github.com/hpark0011/mirror --skill review-pr-hpark0011

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing pull request feedback scattered across GitHub is tedious, and it is hard to tell which comments still apply after new commits. This Skill pulls all review comments for the current branch's PR, checks each one against the actual code, and tells you what still needs action. ## Core Features & Use Cases - Comment Aggregation: Fetches inline code comments and review-level summaries via the GitHub CLI, grouped by file with threaded replies. - Relevance Assessment: Reads the referenced code and diff to classify each comment as still relevant, already resolved, no longer applicable, nitpick, or incorrect. - Actionable Report: Presents a summary table with counts per category, then optionally implements fixes for still-relevant comments. - Use Case: After pushing changes to a branch, run this Skill to see which reviewer concerns remain unaddressed before requesting re-review. ## Quick Start Ask the assistant to check the PR review comments on the current branch and show which ones still need to be addressed.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I see all review comments on a GitHub PR from the command line?▼

Use the GitHub CLI with gh api to query repos/{owner}/{repo}/pulls/{number}/comments for inline comments and /reviews for review summaries. This Skill automates both calls and formats the results grouped by file.

How to check if PR review comments are already resolved?▼

Compare each comment against the current code using git diff between the base branch and HEAD. This Skill reads the referenced files and classifies comments as still relevant, already resolved, or no longer applicable.

Does this work if there is no PR for the current branch?▼

No. The Skill first runs gh pr view to find the PR associated with the current branch. If no PR exists, it reports that to the user and stops without fetching anything.

Can it automatically fix code based on reviewer feedback?▼

Yes, optionally. After presenting the relevance report, the Skill asks whether you want to address still-relevant comments, then reads the affected files and implements the requested changes.

What are the limitations of automated PR comment triage?▼

The relevance assessment depends on reading the current diff and files, so ambiguous or design-level comments may need human judgment. Bot comments are omitted unless they contain actionable feedback.