pr-review

Fetch pull request metadata and diffs to generate a structured review.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the process of reviewing pull requests by fetching PR metadata and diffs, enabling faster, more informed code reviews.

Core Features & Use Cases

  • Triggers on natural language prompts such as "review PR", "review PR #<n>", or "review this branch" to start a PR review.
  • Uses gh CLI to fetch PR head branch and metadata, and git to compute diffs against the base branch, then presents a structured review including potential issues.
  • Supports fallbacks and validations: if the PR isn't found or the diff is empty, it informs the user and stops gracefully.

Quick Start

Ask me to review PR #<number> or simply say "review" to begin the diff-based assessment on the current 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 a pull request review using git diff?

Automate a pull request review by fetching PR metadata and computing diffs against the base branch to present a concise, actionable review with potential issues. Trigger the review using natural language prompts like "review PR #<number>" or simply "review this branch".

Do I need the gh CLI to review a PR?

You need gh CLI to fetch PR head branch and metadata, and git to compute diffs. The skill requires both tools for full functionality but includes graceful fallbacks and validations if a PR is not found or the diff is empty.

What's the best way to review the current HEAD branch before merging?

Review the current HEAD by triggering the skill with a prompt like "review". It validates branch and diff existence, then presents base/target information, diffs, and commit history to inform your merge decisions.

How does a git diff based code review identify potential issues?

A git diff based code review fetches commit history and metadata to deliver a structured assessment of changes. It processes the diff against the base branch to highlight potential issues and provides a concise, actionable review.

What happens if I try to review a PR that does not exist or has an empty diff?

If the PR is not found or the diff is empty, the skill informs the user and stops gracefully. It validates branch and diff existence before delivering the review to prevent errors during the automation process.