Instructions

Run a structured PR review for React / Next.js / TypeScript changes. Prefer actionable comments over rewriting the author's PR.

When to Use

Use when reviewing a pull request, diff, or “look at this PR” request.
Prefer code-assistant for implementing a small fix yourself.
Prefer tdd-vitest / testing-agent when the gap is missing tests, not review tone.
Prefer secure-dependencies when the PR is mostly lockfile/audit policy.

Scope the diff: list touched areas (UI, API, schema, CI, deps). Note what is not in the PR.
Checklist (in order): correctness → security/secrets → data loss → a11y/UX regressions → performance → tests/CI → style only if it blocks maintainability.
React/Next specifics: Server vs Client Components, secrets in client bundles, Server Actions auth, cache invalidation, error/loading coverage for new routes.
Comments: file:line when possible; one issue per comment; suggest a fix shape, do not dump a full alternate PR unless asked.
Defer: for deep React composition/perf rules, point readers at vercel-labs/agent-skills react-best-practices rather than reinventing that catalog here.
Verdict: Approve / Approve with nits / Request changes - with the top 3 blockers only in the summary.