frontend-code-review

Review React/TypeScript/JavaScript files for code quality and performance issues.

Updated Feb 7, 2026

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

Ready to run

npx skills add https://github.com/akaiHuang/faw-creative-studio --skill frontend-code-review-akaihuang

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: frontend-code-review
Source: https://github.com/akaiHuang/faw-creative-studio/tree/main/.claude/skills/frontend-code-review
Command: npx skills add https://github.com/akaiHuang/faw-creative-studio --skill frontend-code-review-akaihuang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams enforce consistent frontend code quality by guiding reviews of React/TS/JS files against a living checklist that spans code quality, performance, and business logic before changes are merged or when inspecting a specific file.

Core Features & Use Cases

Two review modes: pending-change reviews (staged/worktree files) and file-targeted reviews (specific file paths).
Checklist-driven judgments: consults living references in references/code-quality.md, references/performance.md, and references/business-logic.md to surface issues.
Actionable output: reports violations with urgency metadata and suggested fixes, enabling triage and remediation.
Use Case: during a PR, run a pending-change review to catch lint/logic issues before submission, or request a focused review on a single component to tighten risk.

Quick Start

Ask me to review your frontend code files (tsx/js/ts) either for pending changes or a targeted file against the established 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 and performance issues?▼

To review React and TypeScript code, evaluate files against established checklists covering code quality, performance, and business logic. This process identifies violations and provides suggested fixes with urgency scores for effective triage.

Can I run a code review on only staged files before submitting a pull request?▼

Yes, you can run pending-change reviews on staged or working-tree files to catch lint and logic issues before PR submission. This targets only the modified code, ensuring new changes meet quality standards.

What is the best way to check a single React component for performance issues?▼

The best way to check a single component is using a file-targeted review. This inspects specific file paths against performance checklists to identify issues and tighten risk in that isolated module.

Does this frontend code review process support JavaScript files as well?▼

Yes, the frontend code review process supports JavaScript, TypeScript, and React files. It analyzes these file types to surface code quality, performance, and business logic violations.

What specific problem areas are covered during a frontend code review?▼

Frontend code reviews cover specific problem areas including code quality, performance, and business logic. These areas are evaluated against living checklists to produce structured, actionable findings.

How do I fix issues found during a TypeScript code review?▼

To fix issues found during a TypeScript code review, consult the generated report which includes suggested fixes and urgency metadata. This allows you to triage remediation by addressing the highest urgency violations first.