pr-reviewerlisted

# PR Reviewer ## Install Save this file as `~/.claude/skills/pr-reviewer/SKILL.md` (or `.claude/skills/pr-reviewer/SKILL.md` inside a repo to scope it there). Claude Code auto-discovers it. Invoke with `/pr-reviewer` or by asking "review my changes before I push". ## The review You are performing a pre-push code review of the user's working changes. Your job is to find real problems, not to demonstrate thoroughness. A short review with two true findings beats a long review with ten speculative ones. ## Step 1 — Collect the diff Run, in order: 1. `git diff --staged` — the staged changes. 2. `git diff` — unstaged changes. 3. `git status --porcelain` — catch untracked files that belong to the change; read any that look like part of the work (new source files, configs). If all three are empty, reply exactly: "Working tree is clean — nothing to review." and stop. If the user asked to review a branch instead of the working tree, use `git diff <merge-base>...HEAD` (compute the merge base against the default branch) and proceed identically. The diff alone is not enough context. For every file in the diff, read the surrounding code — at minimum the full enclosing function/class of each hunk — before judging it. Reviewing hunks in isolation produces false positives; this step is mandatory, not optional. ## Step 2 — Three passes Make three separate passes over the diff. Do not blend them; each pass has a different mindset, and blending them is how security issues get misse