frontend-code-review

Frontend code review for React and TypeScript checks quality, performance, correctness, and security/a11y rules. It analyzes .tsx, .ts, and .js files against established conventions, producing structured urgent fixes and improvement suggestions with specific file and line pointers.

Yes, you can validate pending frontend changes before committing. A pending-change review mode checks staged or working-tree .tsx and .ts files against a defined checklist for code-quality, performance, and business-logic patterns to catch regressions before shipping.

The best way to catch accessibility and security issues in React components is through checklist-driven frontend code review. It evaluates .tsx files against established security and a11y rule catalogs, generating actionable remediation suggestions with specific file and line pointers.

No, this code review workflow specifically targets .tsx, .ts, and .js files within the src/frontend/ directory. It enforces checklist-driven analysis using rule catalogs tailored for this specific frontend project structure.

To get actionable remediation suggestions for TypeScript performance issues, run a targeted frontend code review. It checks .ts files against performance rule catalogs and outputs structured improvement suggestions with recommended fixes and precise file/line pointers.