← ClaudeAtlas

pr-reviewlisted

Use when reviewing a teammate's pull request for the first time — `/pr-review <PR>`, "review PR
zahidakhyar/skills · ★ 0 · Code & Development · score 72
Install: claude install-skill zahidakhyar/skills
# PR Review First review of someone else's PR. It runs `code-review` and, when the diff calls for them, `security-review` and an `impeccable` UI audit (when that plugin is installed), filters every finding through the review protocol (`${CLAUDE_SKILL_DIR}/references/review-protocol.md`, overridden by a repo `REVIEW.md`), and posts the result as one review: one notification for the author. Every later round is `/recheck`, which finds this review through the `reviewed:` marker it writes. Argument: `/pr-review <PR number|URL> [--comment]`. `--comment` posts the review as soon as step 7 has built it, without showing the draft first. Missing PR → `gh pr list --search "review-requested:@me" --json number,title,author` and ask which one. Run inside the repo checkout; needs `gh` and `jq`. ## 1. State ```bash bash "${CLAUDE_SKILL_DIR}/../recheck/scripts/pr_state.sh" <PR> gh pr view <PR> --json title,body,author,baseRefName,headRefOid,isDraft,files ``` - `baseline_source` is not `"none"` → you reviewed this PR before. Stop and point at `/recheck <PR>`. - `isDraft` → ask once whether to review a draft; the author may not be done. - Author is you (`gh api user -q .login`) → the review `event` must be `COMMENT`. - Repo rules: `git show "origin/<base>:REVIEW.md"` (and `CLAUDE.md`). Read them from the base, so the PR cannot change the rules it is reviewed against. Steps 2, 6 and 7 use them. ## 2. Tier and effort The tier is the body's `## Risk` line (`Low|Medium|High: …`). No such li