reviewing-pull-requestslisted
Install: claude install-skill msewell/agent-stuff
# Reviewing Pull Requests
Follow these phases in order. The user provides a PR number, URL, or
`owner/repo#number`. The repo must be cloned locally and `gh` must be
authenticated.
**Not this skill:** Creating PRs, resolving review feedback, fixing CI
failures, or merging. This skill only *reviews* code changes.
## Phase 1 — Gather context
1. **PR metadata:**
```bash
gh pr view <PR> --json title,body,baseRefName,headRefName,state,labels,author,additions,deletions,changedFiles,reviewRequests,reviews
```
2. **Diff:**
```bash
gh pr diff <PR>
```
If diff exceeds 50 changed files (too large to process as a single
diff without truncation), list files first with
`gh pr diff <PR> --name-only` and read high-risk files individually.
3. **Linked issues** — parse PR body for `Fixes #N`, `Closes #N`,
`Resolves #N`, `Related to #N`. For each:
```bash
gh issue view <N> --json title,body,labels,state
```
4. **Existing review comments** — fetch both PR-level and inline:
```bash
REPO=$(gh repo view --json nameWithOwner -q .nameWithOwner)
gh api --paginate repos/$REPO/issues/<PR>/comments \
--jq '.[] | {body, user: .user.login}'
gh api --paginate repos/$REPO/pulls/<PR>/comments \
--jq '.[] | {path, line, body, user: .user.login}'
```
5. **CI status:**
```bash
gh pr checks <PR>
```
If checks failed: `gh run view <RUN_ID> --log-failed`
## Phase 2 — Understand repo conventions
Read each file if it exists (skip sil