| name | frontend-code-review |
| description | Use when reviewing frontend code changes for correctness, quality, performance, and maintainability risks. |
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.
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, 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).
Required output
When invoked, the response must exactly follow one of the two templates:
Template A (any findings)
Code review
Found urgent issues need to be fixed:
1
FilePath: line
Suggested fix
... (repeat for each urgent issue) ...
Found suggestions for improvement:
1
FilePath: line
Suggested fix
... (repeat for each suggestion) ...
If there are no urgent issues, omit that section. If there are no suggestions, omit that section.
If the issue number is more than 10, summarize as "10+ urgent issues" or "10+ suggestions" and just output the first 10 issues.
Don't compress the blank lines between sections; keep them as-is for readability.
Template B (no issues)
Code review
No issues found.
