pr-reviewlisted

# PR Review ## Goal Produce a maintainer-grade review that prioritizes correctness, regressions, missing tests, security concerns, docs drift, and release risk over style-only feedback. ## When to use - The user asks for a PR review, diff review, or merge readiness check. - A branch or worktree needs review before merge. - Agent-authored changes need an independent risk pass. ## When not to use - The user asks to implement fixes immediately; review only if requested. - The change is only documentation; consider `docs-audit`. - The request is a whole-repo health review; use `repo-health-audit`. ## Inputs to inspect - PR description, changed files, commits, and diff stats. - Relevant source files, tests, docs, CI output, and release notes. - Existing architecture or workflow docs that govern touched areas. ## Review rubric Check behavior changes, API contracts, data migrations, error handling, tests, docs, security-sensitive paths, dependencies, and deployment risk. Read `references/review-rubric.md` for detailed prompts and `references/risk-table-template.md` for report format. ## Workflow 1. Inspect diff stats and changed file names first. 2. Identify user-visible behavior and contract changes. 3. Read only the surrounding code needed to verify risk. 4. Check tests and docs touched by the change. 5. Run or report relevant validation if available. 6. Lead with findings ordered by severity and include file/line evidence. 7. Include a verdict only after findings. ##