pr-review

Fetch GitHub PR metadata and diffs to categorize issues and draft comments.

Updated Aug 8, 2025
One-click install
npx skills add https://github.com/Albarracin-sg/MIS-DOTFILES --skill pr-review-albarracin-sg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/Albarracin-sg/MIS-DOTFILES/tree/main/tools/opencode/skill/pr-review
Command: npx skills add https://github.com/Albarracin-sg/MIS-DOTFILES --skill pr-review-albarracin-sg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews GitHub PRs and leaves human, direct comments.

Core Features & Use Cases

  • PR data fetch & analysis: Retrieve PR title, body, files, and diffs to inform comments.
  • Structured review guidance: Categorize issues (CRITICAL, NEEDS REVIEW, QUESTION) to focus feedback.
  • Comment drafting templates: Provide human, constructive feedback and suggested improvement notes.

Quick Start

When a PR URL is shared or a user asks to review a PR, invoke the review process to generate a human, actionable comment.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I automatically review a GitHub pull request and generate comments?

To review a GitHub pull request, you can share the PR URL to fetch metadata, files, and diffs, which then guides constructive commenting. This process categorizes issues to focus feedback and drafts human, actionable improvement notes.

What is the best way to provide constructive feedback on a pull request?

Providing constructive feedback on a pull request involves categorizing issues into CRITICAL, NEEDS REVIEW, and QUESTION. This structured review guidance ensures your comments are direct, actionable, and maintain a human touch.

How does PR metadata and diff analysis improve code review quality?

PR metadata and diff analysis improve code review quality by retrieving the title, body, and file changes to inform your comments. Analyzing this data allows you to categorize issues accurately and draft targeted, constructive feedback.

Can I categorize pull request issues to focus my code review feedback?

Yes, you can categorize pull request issues to focus code review feedback into CRITICAL, NEEDS REVIEW, and QUESTION tiers. This categorization helps retrieve PR data and structure human, direct comments for suggested improvements.

Do I need to share a pull request URL to start the GitHub review process?

You need to share a pull request URL or explicitly ask to review a PR to start the GitHub review process. Invoking the process fetches the necessary PR metadata, files, and diffs to generate an actionable comment.