frontend-code-review

Name: frontend-code-review
Availability: InStock
Author: JYHTHEGREAT

Flag frontend code quality, performance, and business-logic violations in .tsx, .ts, and .js files.

Updated Aug 27, 2026

Search Tags:#typescript #frontend #react #javascript #quality #lint #code-review

Ready to run

npx skills add https://github.com/JYHTHEGREAT/jyh-system --skill frontend-code-review-jyhthegreat

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: frontend-code-review
Source: https://github.com/JYHTHEGREAT/jyh-system/tree/main/archive/reusable/frontend/skills/frontend-code-review
Command: npx skills add https://github.com/JYHTHEGREAT/jyh-system --skill frontend-code-review-jyhthegreat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Frontend teams often struggle with consistent, thorough reviews of UI code across .tsx, .ts, and .js files, leading to missed quality issues and slower release cycles.

Core Features & Use Cases

Pending-change review: inspect staged/working-tree files slated for commit and identify checklist violations before submission.
File-targeted review: review specific user-named files and report relevant checklist findings.
Reusable references: leverage code-quality, performance, and business-logic rules to guide reviews and prioritize fixes.

Quick Start

Review the specified frontend files and request a structured code-review report following the 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 automate frontend code review for React and TypeScript files?▼

Automate frontend code review by scanning pending changes or targeted .tsx, .ts, and .js files to flag quality, performance, and business-logic violations. The review applies a prioritized checklist to components, hooks, and styling, producing a structured report of findings before submission.

What is the best way to check React component quality before a commit?▼

Checking React component quality before a commit involves inspecting staged working-tree files against a living checklist. This process identifies performance issues and business-logic violations in your TypeScript code, generating a prioritized list of fixes to apply before submission.

How does an automated frontend code review handle hooks and runtime behaviors?▼

Automated frontend code review handles hooks and runtime behaviors by applying targeted rules from built-in performance and business-logic references. It evaluates these specific areas within your pending changes to identify violations and output a structured, prioritized findings report.

Can I review specific TypeScript files instead of all pending changes?▼

You can review specific TypeScript files by targeting user-named files directly. This targeted review inspects the specified components and hooks, applying the same quality and performance checklists to report relevant violations without scanning the entire codebase.

What frontend code violations are prioritized during a code review?▼

Frontend code reviews prioritize violations across code quality, performance, and business logic. By enforcing a living checklist from dedicated reference files, the review categorizes findings in components and styling to help developers resolve the most critical issues first.

When should I use an automated checklist for frontend code review?▼

Use an automated checklist for frontend code review when your team struggles with consistent UI code inspection across .tsx and .js files. It enforces standard quality and performance rules during pending changes, preventing missed issues and accelerating release cycles.