frontend-code-review

Automated frontend code review against a multi-category checklist, supporting both pending-change and targeted file reviews. 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. Suggestion) and groups findings by severity, then by category for prioritized remediation Outputs structured reviews with file paths, line numbers, code snippets, and suggested fixes; prompts user to apply fixes if issues are found

INSTALLATION
npx skills add https://github.com/langgenius/dify --skill frontend-code-review
Run in your project or agent environment. Adjust flags if your CLI version differs.

SKILL.md

$2a

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>

### 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?"

Template B (no issues)

## Code review

No issues found.
BrowserAct

Let your agent run on any real-world website

Bypass CAPTCHA & anti-bot for free. Start local, scale to cloud.

Explore BrowserAct Skills →

Stop writing automation&scrapers

Install the CLI. Run your first Skill in 30 seconds. Scale when you're ready.

Start free
free · no credit card