fe-code-review

To review React code for accessibility and performance, apply a structured four-step workflow that analyzes PR diffs or changed files to identify issues across conventions, React patterns, accessibility, and performance. It consults specialized checklists to recommend concrete improvements.

The best way to audit existing frontend code is applying a multi-faceted review approach that enforces checks from reference checklists covering code conventions and React patterns. This surfaces quality issues and guides improvements in a single pass.

Yes, you can use this frontend code review workflow directly on GitHub PR diffs by providing the diff or code snippet. It applies its scope to changed files, focusing on code conventions, patterns, accessibility, and performance to generate recommendations.

Yes, this code review skill checks React patterns and a11y compliance together. It combines code conventions, React patterns, accessibility checks, and performance considerations into a unified frontend review to ensure comprehensive code quality.

You should use a structured frontend code review because manual checks are often inconsistent and hard to scale. A structured workflow enforces checks from reference checklists, ensuring consistent code quality across conventions, patterns, accessibility, and performance.