review-pr

Reviews GitHub pull requests and resolves all reviewer comments via threads.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/neon-law-foundation/navigator --skill review-pr-neon-law-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/neon-law-foundation/navigator/tree/main/.claude/skills/review-pr
Command: npx skills add https://github.com/neon-law-foundation/navigator --skill review-pr-neon-law-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you perform a complete pull request review without leaving loose ends, so every comment gets a real verdict and every handled thread is closed.

Core Features & Use Cases

  • Independent code review: Read the PR diff and the changed files at the head commit before judging feedback, so your assessment is grounded in the actual code.
  • Comment adjudication: Validate, refute, or mark a finding as won't-fix across inline review comments, bot summaries, and top-level PR comments.
  • Thread closure workflow: Reply to each reviewer comment, apply approved fixes when needed, and resolve review threads so the PR can merge cleanly.
  • Use case: A lawyer or engineer asks you to review a PR with bot feedback and human objections; you trace the code, decide which comments are real, and make sure every thread is answered.

Quick Start

Ask me to review a GitHub pull request by number or URL and I will inspect the code, evaluate every comment, and close out the review threads.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I resolve GitHub pull request review threads automatically after checking the code?

To resolve pull request review threads, you must read the diff and head commit, validate each comment against the actual code, reply to the finding, and resolve the thread via GitHub APIs.

How do I validate bot and human review comments on a GitHub PR?

Validating PR review comments requires reading the changed files at the head commit, assessing the correctness of inline feedback and bot summaries against the real code, and adjudicating each finding.

Can I close every inline PR comment and top-level review thread through the GitHub CLI?

Yes, you can close every inline PR comment and top-level review thread by evaluating the feedback, replying to each reviewer comment, and resolving the handled threads through GitHub APIs.

Do I need to read the entire diff before resolving review comments on a pull request?

Yes, you need to read the PR diff and the changed files at the head commit before judging feedback, ensuring your assessment of review comments is grounded in the actual code.

What is the best way to handle won't-fix pull request comments?

The best way to handle won't-fix pull request comments is to validate or refute the finding by tracing the code, mark it as won't-fix in your reply, and resolve the review thread.

Can this Skill apply approved fixes and resolve review threads for PRs with bot summaries?

Yes, for PRs with bot summaries and human objections, the Skill traces the code, decides which comments are real, applies approved fixes when needed, and resolves the review threads.