local-reviewlisted

# Local PR review Review a PR against what its ticket asked for, verify every finding by running code, and write it all to a local scratchfile — never to GitHub. ## Flow 1. **Target** — first that applies: given PR number (`gh pr view/diff <N>`); current branch's open PR (`gh pr view`); local diff vs base (`git diff <base>...HEAD`). Say which you used. 2. **Spec** — find a ticket reference anywhere: branch name, PR title, PR description. Teams differ; there is no fixed pattern. Fetch the ticket via the Jira/Atlassian MCP tools. MCP missing or ticket unreachable → the PR description becomes the spec. Neither exists → infer intent from the code and say so in the overview. Beyond ticket-hunting, the PR description is not review input — judge the changes, not the pitch. 3. **Big picture** — establish what the project does and what the touched area is for: README, CLAUDE.md, directory layout, the modules around the change. A diff can be locally correct and still wrong for the system. 4. **What changed** — describe the change at business level: "fixes the duplicate image on the product page", never "renamed a to b, added an if". No code in the overview. 5. **Scope check** — ticket vs changes: matches / misses pieces / does unrelated extras. Fundamental mismatch (solves a different problem) → stop and ask whether to review anyway. Anything less → record it in the overview's verdict line, keep going. 6. **Find problems** — correctness (edg