Automated frontend code review against a multi-category checklist, supporting both pending-change and targeted file reviews.
Works with
Triggers on user requests to review frontend files ( .tsx , .ts , .js ) and applies a canonical checklist across Code Quality, Performance, and Business Logic categories
Supports two review modes: pending-change review for staged/working-tree files before commit, and file-targeted review for specific named files
Flags violations with urgency metadata (Urgent vs
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionfrontend-code-reviewExecute the skills CLI command in your project's root directory to begin installation:
Fetches frontend-code-review from langgenius/dify and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate frontend-code-review. Access via /frontend-code-review in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
1
total installs
1
this week
136.4K
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
136.4K
stars
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.
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
anthropics/claude-code
github/awesome-copilot
code-yeongyu/oh-my-opencode
alirezarezvani/claude-skills
asyrafhussin/agent-skills
shadcn/improve
I recommend frontend-code-review for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: frontend-code-review is the kind of skill you can hand to a new teammate without a long onboarding doc.
frontend-code-review has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in frontend-code-review — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: frontend-code-review is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend frontend-code-review for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
frontend-code-review has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in frontend-code-review — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for frontend-code-review matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in frontend-code-review — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 59