frontend-review

Analyzes frontend code quality and generates prioritized reports for common defects and inefficiencies.

7|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill frontend-review-camilooscargbaptista
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-review
Source: https://github.com/camilooscargbaptista/cto-toolkit/tree/main/frontend-review
Command: npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill frontend-review-camilooscargbaptista

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides expert, framework-aware code reviews that surface component architecture flaws, performance regressions, accessibility violations, and TypeScript weaknesses so teams can ship more robust frontends with fewer regressions.

Core Features & Use Cases

  • Component architecture audits: evaluates separation of concerns, reusability, naming, and prop/input design for React and Angular components.
  • Framework-specific checks: inspects React hook correctness, effect cleanup, memoization, and Next.js server/client boundaries; checks Angular change detection, RxJS subscription management, Signals usage, and module lazy-loading.
  • Performance & bundle analysis: identifies unnecessary re-renders, large bundle contributors, image and asset issues, virtualization needs, and suggestions for code-splitting.
  • Accessibility audits: verifies semantic HTML, ARIA usage, keyboard navigation, focus management, and color contrast.
  • TypeScript quality: flags excessive any usage, missing generics, and unsafe API typings.
  • Use Case: run when onboarding a new frontend codebase, preparing a release, or investigating performance or accessibility regressions.

Quick Start

Review the frontend code under src/ and produce a structured report highlighting component architecture, performance bottlenecks, accessibility violations, and TypeScript issues prioritized by severity.

Frequently Asked Questions about frontend-review

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

FAQPage Schema
How do I review React and Angular frontend code for performance bottlenecks and architecture issues?

To review React and Angular frontend code, analyze component architecture, check React hook correctness and Angular change detection, and identify unnecessary re-renders. This process evaluates separation of concerns, memoization, and bundle characteristics to produce prioritized recommendations for performance bottlenecks.

What does a frontend accessibility audit check for in TypeScript and JavaScript projects?

A frontend accessibility audit verifies semantic HTML, ARIA usage, keyboard navigation, focus management, and color contrast. It inspects JSX and TSX files to ensure components meet accessibility standards, identifying violations that hinder keyboard navigation or screen reader interactions.

Can I run code reviews on Vue and Svelte projects or does it only support React and Angular?

Yes, you can review Vue and Svelte projects, as well as Next.js applications. The review process applies to related TypeScript and JavaScript projects by matching file patterns for JSX, TSX, Vue, and Svelte files to evaluate component design and static-analysis heuristics across frameworks.

How do I check TypeScript quality and find unsafe API typings in my frontend codebase?

To check TypeScript quality, scan the codebase for excessive any usage, missing generics, and unsafe API typings. The review flags these TypeScript weaknesses alongside architecture and performance issues, providing a structured report prioritized by severity to help teams ship robust frontends.

Does the code review inspect Angular RxJS subscriptions and change detection strategies?

Yes, the code review inspects Angular RxJS subscription management, change detection strategies, Signals usage, and module lazy-loading. It evaluates these framework-specific patterns to identify potential performance regressions and architectural flaws in Angular applications.

When should I run a frontend code review on my TypeScript project?

You should run a frontend code review when onboarding a new codebase, preparing a release, or investigating performance and accessibility regressions. It requires access to project source files to evaluate hooks, effects, bundle output, and component design for prioritized recommendations.