pr-review

Fetches GitHub pull-request review comments and categorizes them by urgency and type.

20|1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/BrOrlandi/my-claude-skills --skill pr-review-brorlandi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/BrOrlandi/my-claude-skills/tree/main/pr-review
Command: npx skills add https://github.com/BrOrlandi/my-claude-skills --skill pr-review-brorlandi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill fetches PR review comments from GitHub, analyzes them by category (Required Changes, Suggestions, and Questions), and lets you decide which items to resolve.

Core Features & Use Cases

  • Fetch PR review comments (inline threads, resolutions, and file/line context) from a GitHub Pull Request.
  • Analyze and categorize comments into Required Changes, Suggestions, and Questions, and summarize actionable items.
  • Present an actionable summary and apply only the changes approved by the user, preserving the rest of the PR feedback.

Quick Start

Provide a PR number to analyze and let the assistant fetch, categorize, and apply approved changes from PR feedback.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I categorize and resolve GitHub pull request review comments?

Categorizing GitHub pull request review comments is done by fetching inline threads and grouping them into required changes, suggestions, and questions to prepare an actionable resolution plan.

How do I automate applying approved changes from PR feedback?

Automating approved changes from PR feedback requires fetching the GitHub review threads, presenting an actionable summary, and applying only the user-approved code modifications.

Can I fetch GitHub PR inline threads and file context for code review workflows?

Yes, fetching GitHub PR inline threads, resolutions, and file/line context is supported to analyze code review workflows and generate a categorized actionable summary.

What is the best way to streamline addressing required changes in a pull request?

The best way to streamline addressing required changes is analyzing PR feedback by category to isolate mandatory updates, suggestions, and questions before applying user-approved modifications.

Do I need to provide a PR number to analyze code review feedback?

Yes, providing a PR number is required to fetch the pull request data, categorize the review comments, and generate the actionable plan for resolving the feedback.