← ClaudeAtlas

pr-reviewlisted

Review a pull request on GitHub and post the review there — fetch the PR diff, review it for bugs, security, performance, and style, then submit a GitHub review with inline comments and a summary. Use when the user says "review the PR", "make a PR review", "start a PR review", "review PR
real-case/marvin-toolkit · ★ 0 · Code & Development · score 68
Install: claude install-skill real-case/marvin-toolkit
Review a pull request **on GitHub** and submit the review there — a summary plus inline comments anchored to the diff. This is the reviewer side of the PR flow: the author opens the PR (`/marvin:pr-create`), this command reviews it, and `/marvin:pr-resolve` turns the comments into fixes. ## Core principle **Review what changed, post where it can be acted on.** The findings land as a GitHub review tied to specific lines, not as throwaway chat output. Be specific, be actionable, and never post AI/automation attribution. ## Input `$ARGUMENTS` — optional PR number (e.g., `42`). If omitted, detect from the current branch. ## Workflow ### 1. Identify the PR ```bash # If $ARGUMENTS is a number, use it. Otherwise detect from the branch: gh pr view --json number,headRefName,baseRefName,url,title -q '{number,branch:.headRefName,base:.baseRefName,url,title}' ``` If no PR is found, stop: "No open PR found for the current branch. Provide a PR number: `/marvin:pr-review 42`". ### 2. Gather the diff and context ```bash gh pr diff <number> # the unified diff under review gh pr view <number> --json title,body,files # intent + changed-file list ``` Read the key changed files in the working tree for surrounding context — a diff hunk alone rarely shows enough to judge correctness. If the PR references a spec (`.marvin/task/<NNN>-<slug>.md`), read it to ground the review in the intended behavior. ### 3. Review checklist Assess the diff agains