pr-review

Reviews pull requests and diffs against repository conventions with verified findings.

Updated Oct 16, 2025
One-click install
npx skills add https://github.com/jlui17/dotfiles --skill pr-review-jlui17
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/jlui17/dotfiles/tree/main/agents/skills/pr-review
Command: npx skills add https://github.com/jlui17/dotfiles --skill pr-review-jlui17

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often miss repo-specific conventions, contain factual errors, or go stale as the branch moves. This Skill structures PR reviews so findings are grounded in the repository's own declared conventions, fact-checked before posting, and re-verified against the current head. ## Core Features & Use Cases - Convention-grounded review: Discovers conventions starting from the repo's README.md and CLAUDE.md, follows their linked docs, and names which convention docs were applied in the posted review. - Review-and-summarize deliverable: Produces both a prose explanation of prior behavior and a per-file walkthrough of the changes, so readers can judge findings without opening the diff. - Factual precision and freshness checks: Verifies CI state, head SHA, and file:line citations, runs an independent fact-check pass, and re-checks the moving head and sibling PRs right before posting. - Use Case: When asked to re-review a PR after the author pushed fixes, re-verify the head SHA, re-check each prior finding against the new tree, and post an updated review naming the conventions applied. ## Quick Start Review the current pull request against this repository's conventions and post a summary with verified findings.

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 pull request against repo conventions?▼

Start from the repo's README.md and CLAUDE.md, follow their links to convention and reviewer-guidance docs, then check the diff against those rules. Name the convention docs applied in the posted review body.

How to write a PR review summary for reviewers?▼

Explain prior behavior and why it is being replaced, then walk through the changes per file so readers can judge findings without opening the diff. Describe what each piece does at runtime rather than labeling hunks.

Can this skill handle re-reviews after fixes are pushed?▼

Yes. Re-review is a stated use case: re-verify the head SHA, re-check each prior finding against the updated tree, and amend the posted review on the forge if earlier comments went stale.

Why do PR review findings become stale or wrong?▼

The branch and sibling PRs move while the review is written, and unverified claims slip in. Re-check the head right before posting and run an independent fact-check pass on every cited file and quote.

Does this replace a repo's own review methodology skill?▼

No. It applies alongside repo-specific review skills, which own the methodology there. This skill supplies general review principles like grounding, precision, and freshness checks.