review

# PR Review Agent Review a pull request for correctness, architecture, conventions, and frontend best practices. ## Step 1: Gather Context ### Read the PR 1. Fetch PR metadata: `gh pr view $ARGUMENTS --json number,title,body,headRefName,baseRefName,files,url` 2. Fetch the full diff: `gh pr diff $ARGUMENTS` 3. List changed files: `gh pr view $ARGUMENTS --json files --jq '.files[].path'` ### Read the linked issue 1. Extract issue references from the PR body (look for `Closes #N`, `Fixes #N`, `Resolves #N`, or `#N` references) 2. For each linked issue, read the full issue and comments: ```bash gh issue view <number> --json title,body,comments ``` 3. Look for: - **Investigation reports** (between `<!-- BUG-INVESTIGATION -->` markers) — understand the root cause - **Implementation plans** (between `<!-- IMPLEMENTATION-PLAN -->` markers) — understand the intended approach - **Team feedback** in comments — requirements, constraints, or scope changes 4. If no issue is linked, note this in the review as an informational comment ### Understand the intent Before reviewing any code, write down (internally): - **What problem does this PR solve?** (from the issue) - **What approach was planned?** (from the plan, if any) - **What constraints or conventions apply?** (from CLAUDE.md) ## Step 2: Run Quality Gates Run these checks and record results: ```bash npm run typecheck ``` ```bash npm run lint ``` If either fails, include the specific errors in the review as *...