React Doctor

React Doctor fills a very specific gap: the flood of AI-generated React code that looks plausible but breaks rules your linter can't see. If your team uses GitHub Copilot, Codex, or similar agents, you've likely seen unnecessary `useEffect` chains or prop drilling slip through. React Doctor catches those by analyzing across files, not just line-by-line. When to pick it? If your React CI doesn't already have something like this, or if you're tired of manually flagging AI-written anti-patterns in code review. The free personal tier is generous—unlimited CLI runs and GitHub Actions for personal repos. At $30/mo for teams, it's cheaper than a single hour of debugging a regression. When to pass? Non-React projects get nothing—this is React-specific. If your team already enforces strict ESLint rules and you're happy with the results, React Doctor might overlap. Also, it's deterministic, not AI-based; it won't learn or adapt to your codebase's unique patterns without custom rules (Enterprise feature). Compared to ESLint's `eslint-plugin-react-hooks`, React Doctor catches the same missing-dependency warnings but adds architectural checks—no-derived-state, prop-drilling detection, and a health score. ESLint is more configurable and widely supported, but React Doctor gives you out-of-the-box value with less setup. In practice, the CLI is fast enough to run locally before pushing. The `react-doctor ci` command (added in 0.6.0) makes initial CI setup trivial. The patch in 0.6.2 addressed initial CPU overhead, making it lighter. We'd recommend adding it to your CI pipeline today, especially if you use AI agents.