react-doctor

Scan React codebases for lint, dead code, accessibility, performance, and architecture regressions.

10|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/tincopper/neeko --skill react-doctor-tincopper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: react-doctor
Source: https://github.com/tincopper/neeko/tree/main/.claude/skills/react-doctor
Command: npx skills add https://github.com/tincopper/neeko --skill react-doctor-tincopper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

React Doctor helps you catch quality regressions early, before they ship or get committed, by surfacing the most common correctness, accessibility, performance, and architecture issues in React code.

Core Features & Use Cases

  • Regression Checks: Compare recent changes against the rest of the codebase and spot new problems introduced by a feature or bug fix.
  • Code Health Scans: Review lint issues, dead code, accessibility gaps, bundle-size risks, and structural problems in React apps.
  • Use Case: After implementing a new component or refactor, run the skill to verify the change did not reduce the project’s health score and to identify the highest-priority fixes.

Quick Start

Ask the skill to scan your React project and report any regressions or code-quality issues before you commit.

Frequently Asked Questions about react-doctor

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

FAQPage Schema
How do I catch React code quality regressions before committing?

To catch React code regressions before committing, scan your project for lint, dead code, accessibility, performance, and architecture issues. This diff-aware process compares recent changes against the codebase to verify health does not regress.

What is a React code health scan?

A React code health scan reviews lint issues, dead code, accessibility gaps, bundle-size risks, and structural problems in React apps. It reports a score with verbose file-and-line diagnostics to identify priority fixes.

Does this regression checker work on changed files or the entire React project?

This regression checker works on both changed files and the entire React project. It supports diff-aware comparisons to validate that new features or bug fixes do not reduce the overall codebase health score.

When do I need to run a React code quality check?

You need to run a React code quality check during feature finishing, bug fixing, pre-commit reviews, and general code cleanup. It verifies that your recent changes did not introduce new accessibility or performance problems.

What's the best way to find dead code and accessibility issues in React?

The best way to find dead code and accessibility issues in React is to run an automated scan that surfaces structural problems and a11y gaps. It provides file-and-line diagnostics to pinpoint exactly where fixes are needed.