review-prlisted

Review the pull request: $ARGUMENTS Follow this process: **why-not-mechanizable:** review workflow guidance; each step requires reading the PR and judging code quality / intent. 1. **Fetch PR details**: run `gh pr view $ARGUMENTS --json title,body,files,commits,additions,deletions,baseRefName,headRefName` `(review-time: see section note)` 2. **Read the diff**: run `gh pr diff $ARGUMENTS` to see all changes `(review-time: see section note)` 3. **Understand intent**: read the PR description, linked issues, and commit messages before reviewing code `(review-time: see section note)` 4. **Load relevant agents**: based on the files changed, load the appropriate expert agents from `~/.claude/agents/` for domain-specific review `(review-time: see section note)` 5. **Review systematically** using the checklist in @checklist.md `(review-time: see section note)` 6. **Produce structured output** in this format: `(review-time: see section note)` ```markdown ## Summary <1-2 sentence overall assessment> ## Verdict: APPROVE / REQUEST_CHANGES / NEEDS_DISCUSSION <reason> ## Findings ### BLOCKER (must fix before merge) - **[file:line]** - Description. Why it matters. Suggested fix. ### ISSUE (should fix, may approve with commitment to follow-up) - **[file:line]** - Description. Recommendation. ### SUGGESTION (take it or leave it) - **[file:line]** - Description. Alternative approach. ### NIT (style/preference, non-blocking) - **[file:line]** - Description. ### PRAISE (good patt