skills.rest
SoyJuanMa
SoyJuanMaCOMMUNITY
Explore all skills by this author →
GitHub

pr-review

Review GitHub pull requests and categorize findings into CRITICAL, NEEDS REVIEW, or QUESTION.

Updated Jul 10, 2025
Search Tags:#github#review#diff#pr#code-review#comment
One-click install
npx skills add https://github.com/SoyJuanMa/Nvim_Back --skill pr-review-soyjuanma
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/SoyJuanMa/Nvim_Back/tree/main/opencode/skill/pr-review
Command: npx skills add https://github.com/SoyJuanMa/Nvim_Back --skill pr-review-soyjuanma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers quickly produce thoughtful, human-friendly PR feedback instead of robotic checklists, saving time and improving code quality.

Core Features & Use Cases

  • Fetch PR metadata and diff: Retrieve title, body, files, and diff information to understand the PR context.
  • Prioritize issues: Classify findings into CRITICAL, NEEDS REVIEW, or QUESTION and propose concrete next steps.
  • Craft constructive comments: Generate tone-aware, actionable feedback that invites collaboration and growth.
  • Use Case: Given a PR URL, quickly surface the most impactful issues and provide suggested next steps to the author.

Quick Start

Review the provided PR URL or details and produce a concise, human, actionable review comment.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I review a GitHub pull request and get actionable feedback?▼

Reviewing a GitHub pull request involves fetching metadata and diffs to understand context, then categorizing findings into CRITICAL, NEEDS REVIEW, or QUESTION while proposing concrete next steps for the author.

What is the best way to write constructive code review comments on a PR?▼

Writing constructive code review comments requires generating tone-aware feedback that invites collaboration and growth, prioritizing impactful issues and suggesting next steps rather than producing robotic checklists.

Can I prioritize code review findings using GitHub CLI diffs?▼

Yes, you can prioritize code review findings by fetching PR metadata and diffs via GitHub CLI, then classifying issues into CRITICAL, NEEDS REVIEW, and QUESTION categories to guide the author effectively.

Does this GitHub PR review approach work with just a pull request URL?▼

Yes, this GitHub PR review approach works with just a pull request URL, as it fetches the title, body, files, and diff information directly to quickly surface the most impactful issues.

Why use a categorized PR review instead of a standard code checklist?▼

Using a categorized PR review helps developers quickly produce thoughtful, human-friendly feedback instead of robotic checklists, saving time and improving code quality through tone-aware, actionable comments.

Related Skills

Explore More Software Engineering Skills→
x402agentx402agent

review-github-pr

Summarizes GitHub pull requests by distilling diffs and highlighting design decisions.

Community
Intermediate
josemartinrodriguezmortalonijosemartinrodriguezmortaloni

pr-review

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

Community
Intermediate
udecodeudecode
1.2k

reviewing-pr

Automate GitHub pull request reviews with severity-rated feedback.

Official
Intermediate
inbharataiinbharatai
22

code-reviewer

Analyzes code for bugs, security vulnerabilities, performance bottlenecks, and style violations.

Community
Advanced