frontend-code-review

Review frontend .tsx, .ts, and .js files against a predefined checklist.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/jason23452/dify-open-parent_message_id --skill frontend-code-review-jason23452
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-code-review
Source: https://github.com/jason23452/dify-open-parent_message_id/tree/main/.agents/skills/frontend-code-review
Command: npx skills add https://github.com/jason23452/dify-open-parent_message_id --skill frontend-code-review-jason23452

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the review of frontend code, ensuring adherence to established quality, performance, and business logic standards before code submission.

Core Features & Use Cases

  • Pending-change review: Inspects staged files for checklist violations.
  • File-targeted review: Reviews specific files named by the user.
  • Checklist adherence: Enforces rules defined in references/ for code quality, performance, and business logic.
  • Use Case: A developer can request a review of their recently modified .tsx files to catch potential bugs and ensure consistency with project standards before pushing to the main branch.

Quick Start

Review the frontend code in the current pending changes against the project's checklist.

Frequently Asked Questions about frontend-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review React and TypeScript code for quality before committing?

Review React and TypeScript code by checking pending changes or targeted .tsx and .ts files against a checklist covering code quality, performance, and business logic, flagging violations with suggested fixes.

What is the best way to automate frontend code checks for staged files?

Automate frontend code checks by running a pending-change review that inspects staged .js, .ts, and .tsx files, enforcing predefined rules and returning violations with urgency metadata.

Can I review specific frontend files instead of all pending changes?

Yes, you can perform a file-targeted review by naming specific .tsx, .ts, or .js files, which checks them against the checklist for code quality, performance, and business logic violations.

Does this code review tool check for performance and business logic issues?

Yes, the code review tool checks for performance and business logic issues by evaluating frontend files against reference documents that define detailed rules for each category.

How does the frontend code review process flag violations?

The frontend code review process flags violations by assigning urgency metadata to each issue and providing suggested fixes based on the predefined checklist rules.

Are there limitations to reviewing frontend code with this checklist approach?

The checklist approach limits reviews to .tsx, .ts, and .js files, relying on predefined reference rules for code quality, performance, and business logic rather than custom or dynamic analysis.