frontend-code-reviewer

To review a React pull request for accessibility and TypeScript strictness, submit the diff to a frontend code reviewer. It analyzes WCAG 2.1 AA compliance, React correctness, type safety, performance, and test quality, returning severity-labeled findings grouped by phase.

A frontend code review checks Next.js components for React anti-patterns, TypeScript unsafety, accessibility violations, performance regressions, and weak test coverage. It evaluates single components or full diffs and produces a merge verdict with explicit uncertainty notes.

Yes, you can run a targeted WCAG 2.1 AA accessibility audit on a code snippet. The review process supports targeted audits alongside full PR assessments, identifying specific access issues and returning structured findings with severity labels.

To get a merge verdict for a frontend diff, request a phase-structured review covering accessibility, React correctness, TypeScript strictness, performance, and test quality. The review outputs an Approve, Approve with minor comments, Request Changes, or Block decision with rationale.

This code review process works with both single-component checks and full pull requests. It applies to targeted audits like React pattern validations and WCAG checks, as well as comprehensive diff reviews across React, TypeScript, and Next.js contexts.

Common React correctness and performance issues caught during frontend reviews include anti-patterns, type unsafety, and regressions. The review applies a structured five-phase analysis to identify these problems before merging, producing severity-labeled findings.