react-component-diagnosis

Diagnoses a single React component across seven design dimensions with evidence-based scores.

Updated Jan 10, 2026
One-click install
npx skills add https://github.com/Rabbit-Ivan/Ivan-skills --skill react-component-diagnosis-rabbit-ivan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: react-component-diagnosis
Source: https://github.com/Rabbit-Ivan/Ivan-skills/tree/main/skills/react-component-diagnosis
Command: npx skills add https://github.com/Rabbit-Ivan/Ivan-skills --skill react-component-diagnosis-rabbit-ivan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? React components often accumulate design debt that is invisible to a quick directory scan: unstable useMemo dependencies, props-to-state sync anti-patterns, per-frame recomputation, and leaky type boundaries. This Skill performs a line-by-line health check of one component and turns those findings into a structured, actionable diagnosis report. ## Core Features & Use Cases - Seven-Dimension Scorecard: Scores consumer API, data flow, testability, extensibility, performance, mental model, and boundaries & contracts from 1-5, each backed by concrete code citations in filename:line format. - Frame-Level Performance Analysis: For animation or high-frequency rendering components, traces which computations execute every frame, detects uncached temporary objects, and checks whether useEffect cleanups actually cancel async work. - Prioritized Recommendations: Outputs P0/P1/P2 improvement suggestions, each with problem, impact, direction, and effort estimate (small/medium/large), plus 2-3 design highlights worth spreading. - Use Case: Point the Skill at a 2000-line composite component directory and ask "is this component well designed" to receive a full scorecard, per-dimension analysis with code evidence, and a refactor roadmap. ## Quick Start Ask the AI to diagnose the design quality of the React component in a specific directory or .tsx file and produce the seven-dimension report.

Frequently Asked Questions about react-component-diagnosis

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

FAQPage Schema
How do I review the design quality of a React component?▼

Point the Skill at the component directory or .tsx file and ask for a diagnosis. It reads every source file including hooks and utils, then scores seven dimensions such as consumer API, data flow, and performance with concrete filename:line evidence.

How to find unnecessary re-renders in a React component?▼

The performance dimension checks for unstable useMemo and useEffect dependencies, objects recreated every render, unsplit Context, and heavy computation inside the render loop. For animation components it performs frame-level analysis of per-frame computation and GC pressure.

Does this work for whole codebase architecture review?▼

No, it focuses on a single React component. For whole-repo architecture, module boundaries, or cross-file dependency analysis, the Skill itself routes you to architecture-level skills such as hai-architecture or improve-codebase-architecture.

When should I not use a component diagnosis report?▼

Avoid it when the target is not a React component, such as a utility file or service, or when you only want type-safety tightening, naming advice, or generic code smell cleanup. Those cases route to ts-type-safety-reviewer, hai-naming, or clean-code-reviewer.

What does the component diagnosis report contain?▼

The report includes a seven-dimension scorecard with star ratings, per-dimension strengths and weaknesses citing code locations, 2-3 design highlights, and P0/P1/P2 recommendations with problem, impact, suggestion, and effort estimates.