pr-fixlisted

# PR Review, Fix, and Document Review a pull request end-to-end: identify issues, post them as a GitHub comment, apply the fixes, push, and document what was changed. **Input:** "$ARGUMENTS" ## Workflow ### 1. Identify the PR - If a PR URL or number is provided, use it - Otherwise detect from current branch: `gh pr view --json number,url,headRefName,baseRefName,state` - If the PR is closed, draft, or merged — stop and tell the user - If no PR found — stop and tell the user ### 2. Gather Context - Get the diff: `gh pr diff <number>` - Get changed files: `gh pr diff <number> --name-only` - Read CLAUDE.md files in the repo root and in directories containing changed files - Get PR metadata: `gh pr view <number> --json body,title` ### 3. Review the Changes Read each changed file and identify: - **Bugs** — logic errors, off-by-ones, null/undefined handling, race conditions - **Cross-file correctness** — when the diff references a type, function, or property defined in another file, follow the import and verify it actually exists and has the expected shape. Don't trust that `obj.field` is valid just because the syntax looks right — read the type/interface definition. - **CLAUDE.md violations** — project convention breaches - **Security issues** — injection, auth gaps, data exposure - **Broken error handling** — only at system boundaries, not defensive over-validation **Critical: trace references across file boundaries.** The diff only shows what changed, but bugs often liv