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: 1. **Pending-change review** – inspect staged/working-tree files slated for commit and flag checklist violations before submission. 2. **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/code-quality.md), [references/performance.md](references/performance.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 1. Open the relevant component/module. Gather lines that relate to class names, React Flow hooks, prop memoization, and styling. 2. For each rule in the review point, note where the code deviates and capture a representative snippet. 3. Compose the review section per the template below. Group violations first by **Urgent** flag, then by category order (Code Quality, Performance, Business Logic). ## Required output When invoked, the response must exactly follow one of the two templates: ### Template A (any findings) ``` # Code review Found <N> urgent issues need to be fixed: ## 1 <brief description of bug> FilePath: <path> line <line> <relevant code snippet or pointer> ##...