React Doctor

React Doctor is a deterministic linter built for React codebases. Run it from your project root with `npx react-doctor@latest` and it detects your framework, React version, and rule set, then prints a health score alongside every issue it found — sorted so you handle security risks and performance regressions before lower-risk diagnostics. It supports React, Next.js, Vite, TanStack, React Native, Expo, and Preact projects. Where it earns its keep is cross-file reasoning: derived state via useEffect, render loops, prop drilling you could replace with Context, plus repeated JSX subtrees that likely belong in a shared component. That last category matters for codebases growing sideways — React Doctor measures complex components and flags duplicated UI concepts, churn ESLint doesn't hunt across files. It also pulls dependency supply-chain checks and accessibility findings. The shipped workflow targets teams running AI coding agents — "Your agent writes bad React. This catches it." Install it for your coding agent (Claude Code and Cursor hooks run once at the end of an agent turn), scan after React changes, then add the same scan to CI with `npx react-doctor@latest ci install`, which writes `.github/workflows/react-doctor.yml` and reports new PR findings without blocking merge by default. Use `react-doctor ci config` for a harder gate; `--scope changed` compares your branch against its merge base and reports only new diagnostics. Against ESLint the differentiator is cross-file analysis and CI gating, not raw rule volume — it respects .gitignore, adopts your existing ESLint or oxlint JSON config, and ships standalone oxlint and ESLint plugins so it sits beside the linter you already run. The newer React Bench surface compares how different models perform on React tasks.