frontend-code-review

Frontend Code Review

Intent

Use this skill whenever the user asks to review frontend code (especially .tsx, .ts, or .js files). Support two review modes:

- Pending-change review – inspect staged/working-tree files slated for commit and flag checklist violations before submission.

- File-targeted review – review the specific file(s) the user names and report the relevant checklist findings.

Stick to the checklist below for every applicable file and mode.

Checklist

See references/code-quality.md, references/performance.md, references/business-logic.md for the living checklist split by category-treat it as the canonical set of rules to follow.

Flag each rule violation with urgency metadata so future reviewers can prioritize fixes.

Review Process

- Open the relevant component/module. Gather lines that relate to class names, React Flow hooks, prop memoization, and styling.

- For each rule in the review point, note where the code deviates and capture a representative snippet.

- Compose the review section per the template below. Group violations first by Urgent flag, then by category order (Code Quality, Performance, Business Logic).