Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From claude-forge
Reviews frontend files (JSX, TS, JS) for code quality, performance, and business logic violations using a structured checklist. Supports pending-change and file-targeted reviews.
npx claudepluginhub sangrokjung/claude-forge --plugin claude-forgeHow this skill is triggered — by the user, by Claude, or both
Slash command
/claude-forge:frontend-code-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill whenever the user asks to review frontend code (especially `.tsx`, `.ts`, or `.js` files). Support two review modes:
Reviews changed React/TypeScript frontend code, auto-detects technologies (Remix, Zustand, shadcn/ui, etc.), and loads specialized sub-skills for targeted review. Optionally parallelizes with agents.
Reviews frontend code across architecture, type safety, rendering/state, style, accessibility, maintainability, testability, and security. Outputs graded reports (CRITICAL to LOW) with file/line references and fix suggestions.
Performs code quality reviews for patterns, security, performance, correctness, bugs, and untested code. Reports issues with file:line citations and delegates to fix, test, sentinel skills.
Share bugs, ideas, or general feedback.
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:
## 1 <brief description of suggestion>
FilePath: <path> line <line>
<relevant code snippet or pointer>
### Suggested fix
<brief description of 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.
If you use Template A (i.e., there are issues to fix) and at least one issue requires code changes, append a brief follow-up question after the structured output asking whether the user wants you to apply the suggested fix(es). For example: "Would you like me to use the Suggested fix section to address these issues?"
## Code review
No issues found.