Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ohh-889/frontend-code-review
Trigger when the user requests a review of frontend files (e.g., `.tsx`, `.ts`, `.js`). Support both pending-change reviews and focused file reviews while applying the checklist rules.
Passed 16 of 20 test cases with the skill, and 7 of 20 without it.
and 13 more in the full report
11 fixed7 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
Review `src/views/ProfileView.tsx` where line 32 uses standard anchor tags instead of React Router navigation links. What subsection header precedes the recommended change?
| Checked | Without skill | With skill |
|---|---|---|
| The fix recommendation is introduced with `### Suggested fix`. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill whenever the user asks to review frontend code (especially .tsx, .ts, or .js files). Support two review modes:
Stick to the checklist below for every applicable file and mode.
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.
When invoked, the response must exactly follow one of the two templates:
# Code review
Found <N> urgent issues need to be fixed:
## 1 <brief description of bug>
FilePath: <path> line <line>
<relevant code snippet or pointer>
### Suggested fix
<brief description of suggested fix>
---
... (repeat for each urgent issue) ...
Found <M> suggestions for improvement:
test cases passed, vs 7 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.