pr-overview

Reviews pull requests from diffs, surrounding code, checks, and review state.

Updated Jul 17, 2026
One-click install
npx skills add https://github.com/guneysol/agent-configs --skill pr-overview-guneysol
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-overview
Source: https://github.com/guneysol/agent-configs/tree/main/agents/skills/pr-overview
Command: npx skills add https://github.com/guneysol/agent-configs --skill pr-overview-guneysol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Understanding and reviewing a pull request requires reading the diff, surrounding code, linked issue, checks, and review threads, then turning all of that into a clear verdict and actionable comments. This Skill automates that analysis so reviewers get a structured explanation of the problem, the solution, and every finding with exact file and line locations. ## Core Features & Use Cases - Evidence-based PR explanation: Reconstructs the behavior before the PR, the concrete problem, and how the changes solve it, treating the PR description as stated intent rather than proof. - Classified review findings: Labels findings as blocker, issue, question, or nit, separating code blockers from merge-state blockers like failing checks or unresolved threads. - Paste-ready GitHub comments: Produces a copy/paste review comment with exact path/to/file.ts:42 locations in a brief, collaborative, lowercase tone. - Use Case: A reviewer opens a large PR touching authentication logic. The Skill traces the changed paths through callers and tests, flags a stale-cache blocker at an exact line, lists merge-state blockers, and outputs a ready-to-post review comment plus a test plan. ## Quick Start Ask the assistant to review a pull request and give a merge recommendation with findings and a copy-paste review comment.

Frequently Asked Questions about pr-overview

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

FAQPage Schema
How do I review a pull request from its diff?▼

Read the title, linked issue, full diff, and surrounding code, then trace changed paths through callers, contracts, and tests. Classify findings as blocker, issue, question, or nit, and give each an exact path and changed line number.

How to write a good GitHub review comment?▼

Keep it brief, specific, and collaborative, stating the triggering condition and impact rather than a bare instruction. Include the exact file and line location, and avoid demanding wording like "must" or "fix this".

What is the difference between a code blocker and a merge-state blocker?▼

A code blocker is a demonstrated correctness, security, or data-loss problem in the changed code. A merge-state blocker is a failing required check, missing approval, unresolved thread, or conflict, which does not automatically mean the code is defective.

Can a PR review rely on the PR description and passing checks?▼

No. The PR description and linked issue state intent, not proof of behavior, and passing checks do not guarantee correctness. The diff and surrounding code must be treated as the source of truth.

What are the limitations of automated pull request review?▼

Review quality depends on available evidence; prior behavior or intent sometimes cannot be proven from the diff alone. In those cases the finding should be raised as a question rather than asserted as a defect, and line numbers must never be invented.