frontend-code-review

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

Updated Mar 27, 2024
One-click install
npx skills add https://github.com/boomNDS/new_portfolio --skill frontend-code-review-boomnds
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-code-review
Source: https://github.com/boomNDS/new_portfolio/tree/main/.agents/skills/frontend-code-review
Command: npx skills add https://github.com/boomNDS/new_portfolio --skill frontend-code-review-boomnds

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Review frontend code efficiently by applying a consistent, multi-category checklist to catch issues in files like .tsx, .ts, and .js, for both pending changes and targeted files.

Core Features & Use Cases

  • Applies standardized rules from the code quality, performance, and business-logic references to frontend components.
  • Supports pending-change reviews (staged/working-tree files) and file-targeted reviews (specific file paths) with urgency-tagged findings.
  • Produces a structured review template with categorized results to guide fixes before merge.

Quick Start

Provide the frontend file path or specify the pending-change option to initiate a structured code review.

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 frontend JavaScript and TypeScript code for quality issues?

To review frontend JavaScript and TypeScript code for quality issues, apply a structured checklist that identifies and reports problems in .js, .ts, and .tsx files, aggregating findings by urgency and category to guide fixes before merge.

Can I run a code review on staged commits instead of specific files?

Yes, you can run a code review on staged commits instead of specific files. The review supports both pending changes in the working tree and targeted file paths to identify performance and business-logic issues.

What is the best way to enforce performance rules in a TypeScript codebase?

The best way to enforce performance rules in a TypeScript codebase is applying a standardized checklist that evaluates code quality, performance, and business logic, producing categorized results with urgency tags.

Does a structured frontend code review work with TSX files?

Yes, a structured frontend code review works with TSX files. It analyzes JavaScript and TypeScript files including TSX, applying strict adherence to quality and performance rules to report categorized findings.

How do I prioritize fixes after identifying code quality issues in frontend files?

You prioritize fixes after identifying code quality issues in frontend files by using the structured review template, which automatically aggregates and orders findings by urgency and category.