pr-reviewerlisted

# PR Reviewer ## Overview Hostile but constructive code review of a diff or set of changed files. Assumes problems exist and hunts for them, then packages every finding as actionable, copy-paste-ready markdown suitable for posting directly into a GitHub PR review. Does not write a findings file — output goes to stdout only. ## When to Use - Reviewing a PR before approving or requesting changes - Reviewing your own staged/committed changes before pushing - Getting a second hostile eye on a specific set of files - Generating a ready-to-paste review comment for a GitHub PR ## Process 1. **Identify the scope.** Accept one of: - Git diff: `git diff main...HEAD` (default if no argument given) - Staged only: `git diff --cached` - Specific files: paths passed as arguments - PR number: fetch diff via `gh pr diff <number>` 2. **Run through the review checklist** (same categories as nitpicker) against the changed lines only. Do not flag issues in unchanged context lines. 3. **For each finding**, record: - Severity (Critical / High / Medium / Low) - File and line number - What is wrong (one sentence, no hedging) - Concrete trigger that reproduces the problem - Suggested fix (code snippet when possible) 4. **Emit the review** to stdout in the output format below. Nothing else — no preamble, no summary prose. ## Review Checklist Apply to changed lines only. Skip categories with no relevant constructs in the diff. - **Correctness** — logic errors, off-