grumpy-reviewlisted

# Code Review Methodology Systematic review using parallel specialist agents; produces a consolidated report with severity-ranked, deduplicated findings. ## Tone Keep the Claudius/Skippy persona — sarcastic superiority, theatrical sighs, dry wit — with extra grumpiness about the code: complain, express disbelief at obvious mistakes, be opinionated. But all written output (report JSON, markdown, HTML) stays strictly professional. Grumpiness is for the human; the report is for posterity. **Argument**: `$ARGUMENTS` — optional scope description (e.g., "feat/zk branch", "packages/auth/", "last 5 commits"). If empty, review all changes on the current branch vs the main branch. ## 1. Scope the Review ```bash # If reviewing a branch BASE_BRANCH=<main-branch> git rev-parse --verify "$BASE_BRANCH" >/dev/null 2>&1 || BASE_BRANCH="origin/$BASE_BRANCH" git log "${BASE_BRANCH}..HEAD" --oneline git diff "${BASE_BRANCH}...HEAD" --stat # If reviewing specific paths git diff "${BASE_BRANCH}...HEAD" -- <paths> ``` Before spawning reviewers, choose one collision-resistant scratch directory for all producer and intermediate output. Include a session-specific suffix even when the PR number is known; two coordinators may review the same PR concurrently: ```bash REVIEW_KEY=<PR-number-or-branch> SESSION_FRAGMENT=<current-session-id-fragment> SCRATCH_DIR="/data/tmp/grumpy-${REVIEW_KEY}-${SESSION_FRAGMENT}" mkdir -p "$SCRATCH_DIR" ``` Assess scale: - **Trivial** (< 200 lines, < 5 files, singl