pr-review

Reviews GitHub pull request diffs and posts inline comments with a summary review.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/real-case/marvin-toolkit --skill pr-review-real-case
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/real-case/marvin-toolkit/tree/main/plugins/marvin/skills/pr-review
Command: npx skills add https://github.com/real-case/marvin-toolkit --skill pr-review-real-case

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing pull requests manually means juggling diffs, context files, and GitHub's review UI, and findings often end up as unstructured chat notes instead of actionable inline comments. This Skill fetches the PR diff, reviews it against a structured checklist, and submits a single GitHub review with line-anchored comments. ## Core Features & Use Cases - Structured review checklist: Assesses the diff across correctness, security, performance, error handling, readability, testing, and scope. - Severity-ranked inline comments: Anchors each finding to a specific file and line in the diff, tagged as critical, warning, or suggestion. - GitHub review submission: Posts one review via the GitHub API with the appropriate event (COMMENT, REQUEST_CHANGES, or APPROVE), respecting the rule that you cannot approve your own PR. - Use Case: A teammate opens PR #42 and asks for a review. Run the command, confirm the drafted review, and the findings land as inline comments the author can resolve with /marvin:pr-resolve. ## Quick Start Ask the assistant to review PR 42 on GitHub and post the review with inline comments.

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 GitHub pull request from the command line?▼

Use the gh CLI to fetch the diff with gh pr diff and submit a review through the GitHub reviews API with gh api. This Skill automates that flow, posting one review with inline comments anchored to changed lines.

How do I add inline comments to a GitHub PR review?▼

Inline comments are posted via the GitHub reviews API by specifying each comment's path, line, and side in a JSON payload. The line must be part of the diff, or the API rejects the comment.

Can I approve my own pull request on GitHub?▼

No, GitHub forbids approving or requesting changes on a PR you authored. For self-authored PRs, this Skill uses the COMMENT event so observations are posted without a verdict.

Why does my GitHub review comment fail with a line error?▼

The API rejects comments whose path and line are not part of the PR diff. Keep inline comments on changed lines and raise anything outside the diff in the review summary body instead.

What is the difference between pr-review and a local code review?▼

This Skill posts findings to GitHub as a public review tied to the PR. For a local, read-only pre-commit review that leaves no trace on GitHub, use the /code-review command or the marvin-auditor agent instead.