pr-review

Fetch GitHub PR diffs and post categorized, human-centric review comments.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/josemartinrodriguezmortaloni/opencode-config --skill pr-review-josemartinrodriguezmortaloni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/josemartinrodriguezmortaloni/opencode-config/tree/main/skill/pr-review
Command: npx skills add https://github.com/josemartinrodriguezmortaloni/opencode-config --skill pr-review-josemartinrodriguezmortaloni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the GitHub Pull Request review process, ensuring that feedback is constructive, human-centric, and focused on critical issues, rather than superficial style preferences.

Core Features & Use Cases

  • Automated PR Analysis: Fetches PR details and diffs using GitHub CLI.
  • Categorized Feedback: Focuses comments on critical issues, necessary reviews, and clarifying questions, ignoring minor stylistic points.
  • Human-like Tone: Crafts comments that are conversational and helpful, like a senior colleague.
  • Use Case: When a developer submits a PR, this skill can be invoked to provide a thorough, yet concise, review, highlighting potential bugs or design flaws and suggesting improvements in a collaborative manner.

Quick Start

Use the pr-review skill to analyze the pull request with number 123.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I automate GitHub pull request reviews to focus on critical code issues?

Automated GitHub pull request reviews fetch PR details and diffs to categorize feedback into critical issues, necessary reviews, and clarifying questions. This approach ignores stylistic nitpicks and focuses on actionable code quality feedback.

What is the best way to provide human-centric code review comments on a pull request?

Human-centric code review comments are crafted conversationally like a senior colleague, highlighting potential bugs or design flaws. This method categorizes issues into critical, needs review, or question tiers to suggest improvements collaboratively.

Does automated PR analysis ignore stylistic nitpicks during code review?

Yes, automated PR analysis explicitly avoids stylistic nitpicks during code review. It focuses solely on posting human-centric, actionable feedback categorized into critical issues, necessary reviews, and clarifying questions.

Can I use GitHub CLI to fetch PR diffs for automated code review?

Yes, you can use GitHub CLI to fetch PR diffs for automated code review. The process retrieves pull request information and diffs, categorizes identified issues, and posts constructive comments to ensure code quality and author growth.

How do I categorize pull request feedback into critical issues and questions?

You categorize pull request feedback by analyzing the fetched PR diff and sorting issues into critical, needs review, or question categories. This ensures comments remain concise, actionable, and focused on significant design flaws rather than minor style preferences.

Why does my automated code review post superficial style comments instead of actionable feedback?

Automated code review should avoid superficial style comments by categorizing issues into critical, needs review, or question buckets. Focusing on human-centric, actionable feedback prevents stylistic nitpicks and promotes constructive code quality improvements.