skills.rest
grojeda
grojedaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pr-review

Automate pull request reviews by extracting GitHub data and analyzing code diffs.

25|4|Updated May 4, 2026
Search Tags:#git#diff analysis#code review#pull request#github#quality assessment
One-click install
npx skills add https://github.com/grojeda/opencode-config --skill pr-review-grojeda
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/grojeda/opencode-config/tree/main/skills/pr-review
Command: npx skills add https://github.com/grojeda/opencode-config --skill pr-review-grojeda

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the review process for pull requests and local branch differences by providing structured commands, evidence collection, and assessment frameworks.

Core Features & Use Cases

  • PR Data Gathering: Retrieve detailed PR information such as title, body, files changed, commits, and checks from GitHub.
  • Diff and Change Analysis: Generate diffs, review file statuses, and summarize code changes between branches or commits.
  • Review Assistance: Assist reviewers in verifying correctness, regression risks, and missing tests, enabling fast, thorough evaluations.
  • Use Case: A developer uses this Skill during PR review to quickly obtain all relevant data, identify potential issues, and provide structured feedback.

Quick Start

Use the pr-review skill to analyze the current branch diff compared to the main branch.

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 review and diff analysis?▼

To automate GitHub pull request review, this Skill extracts PR data, file changes, and commit history using GitHub CLI, git, and ripgrep, then assesses code quality and regression risks to provide structured feedback.

What is the best way to check branch differences for missing tests and regression risks?▼

Checking branch differences for regression risks involves generating diffs and summarizing code changes between commits, which this Skill does by collecting evidence with ripgrep to evaluate correctness and testing adequacy.

Do I need GitHub CLI and ripgrep installed to review pull requests locally?▼

Yes, you need GitHub CLI, git, and ripgrep installed locally, as this Skill relies on these specific tools to gather pull request data, generate diffs, and collect evidence for comprehensive code quality assessments.

Can I use this to gather GitHub PR data like commit history and file statuses for code review?▼

Yes, you can use this to retrieve detailed GitHub PR data including titles, bodies, changed files, commits, and checks, enabling fast and thorough evaluations of branch differences and code quality.

What are the limitations of using git diff analysis for automated code quality assessment?▼

Git diff analysis provides evidence-based summaries of code changes but relies on local tool availability and does not automatically fix issues, meaning reviewers must still interpret the structured findings to ensure correctness.

Related Skills

Explore More Software Engineering Skills→
wyattjohwyattjoh
1

pr-status

Visualize GitHub pull request stacks and identify stale local branches.

Community
Intermediate
ybbms777ybbms777
1

resolve-pr-feedback

Process GitHub pull request review feedback end-to-end with gh and jq.

Community
Advanced
dhntdhnt

code-review

Review pull request diffs and report evidence-backed findings by severity.

Official
Intermediate
jmaglyjmagly
175

pr-reviewer

Automate GitHub pull request reviews for quality, security, and standards issues.

Community
Advanced