react-doctor

Scans React codebases for security, performance, and architecture issues with a health score.

Updated Sep 7, 2026
One-click install
npx skills add https://github.com/raphaelmans/spectralpointengineering --skill react-doctor-raphaelmans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: react-doctor
Source: https://github.com/raphaelmans/spectralpointengineering/tree/main/.skillshare/skills/react-doctor
Command: npx skills add https://github.com/raphaelmans/spectralpointengineering --skill react-doctor-raphaelmans

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? React codebases accumulate lint violations, accessibility gaps, bundle bloat, and architecture problems that are hard to catch manually before committing. This Skill runs automated diagnostics and produces a 0-100 health score so regressions are caught before they ship. ## Core Features & Use Cases - Regression checks on changed code: Run a scoped scan after edits to verify the health score did not drop before committing. - Full-codebase triage: Execute a complete scan, then fix issues by severity using the canonical scan-filter-triage-fix-validate playbook fetched from react.doctor. - Focused design and runtime audits: Run design-only diagnostics for UI composition and accessibility, or record a DevTools trace in an isolated Chrome profile to diagnose slow interactions with per-component render evidence. - Rule configuration: Explain, disable, retune, or category-toggle rules via rules subcommands that edit doctor.config.* in place. - Use Case: After refactoring a dashboard page, run the changed-scope scan, see the score dropped due to a new no-array-index-as-key violation, explain the rule, fix it, and re-validate before committing. ## Quick Start Ask the assistant to run react-doctor on the changed files and report whether the health score regressed.

Frequently Asked Questions about react-doctor

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

FAQPage Schema
How do I check React code for issues before committing?

Run npx react-doctor@latest --verbose --scope changed to scan only code modified versus the base branch. The command reports affected files and line numbers per rule and shows whether the 0-100 health score regressed, so you can fix issues before committing.

How do I disable or configure a React lint rule?

Use npx react-doctor@latest rules explain <rule> to understand it first, then apply the narrowest control: rules disable, rules set <rule> warn, rules category off, or rules ignore-tag. These commands edit doctor.config.* or package.json#reactDoctor in place while preserving formatting.

Can react-doctor diagnose runtime performance problems?

Yes. Run npx react-doctor@latest scan <url> --format json to open an isolated Chrome profile, record a DevTools trace while you reproduce the slow interaction, and outline rendering components. Use --cdp with an existing remote-debugging Chrome session if you need authenticated browser state.

What is the difference between changed, lines, and full scan scopes?

The default full scope scans the entire codebase, --scope changed reports only issues introduced versus the base branch, and --scope lines narrows results to just the modified lines. Changed scope suits pre-commit regression checks; full scope suits cleanup passes.

When should I not disable a noisy rule?

Avoid disabling when you only want to hide findings from PR comments, scores, or CI gates. Instead edit the surfaces config (surfaces.prComment.excludeRules, surfaces.score.excludeTags) so the rule still runs locally while staying out of those outputs.