improve-react
Survey a whole React codebase as a senior React engineer, using React Doctor's scan as evidence, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use when the user asks to "improve the React code", "audit this codebase", "make this app faster / more robust", or wants a roadmap of fixes rather than a review of a single diff. For a regression check or a fix-it-now pass, use the `react-doctor` skill instead.
Profile →npx skills add millionco/react-doctor --skill improve-react --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Improving React An advisor skill modeled on the audit-then-plan workflow: use the capable model for the part where judgment compounds — reading React Doctor's findings, deciding which actually matter, and writing the spec — and hand execution to any agent, including cheaper models. It does ONE thing: survey a React codebase, then produce prioritized findings and implementation plans. It is **not** the `react-doctor` skill: - `react-doctor` runs the scanner, checks the score didn't regress, and (via `/doctor`) fixes the working tree directly. - `improve-react` is read-only. It leans on React Doctor's scan as machine-verified evidence, adds the leverage judgment a static tool can't, and writes plans a cheaper agent executes later. It never edits source. The rule catalog with the five audit categories lives in [AUDIT.md](AUDIT.md). The plan format lives in [PLAN-TEMPLATE.md](PLAN-TEMPLATE.md). Load them when you audit and when you write plans. ## Operating Posture You are a senior React engineer with a brutal eye for what ships to users. React Doctor already lists what is _technically_ wrong; your job is to find the work with the highest leverage — the unstable context value that re
- Operating Posture
- Hard Rules
- The canonical fix is not yours to invent
- Workflow
- Phase 1 — Recon (always first)
- Phase 2 — Audit (parallel)
- Phase 3 — Vet, prioritize, confirm
- Phase 4 — Write plans
- Invocation Variants
- Tone
npx react-doctor@latest --json --json-out react-doctor-report.json
What does the improve-react skill do?
Survey a whole React codebase as a senior React engineer, using React Doctor's scan as evidence, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use when the user asks to "improve the React code", "audit this codebase", "make this app faster / more robust", or wants a roadmap of fixes rather than a review of a single diff. For a regression check or a fix-it-now pass, use the `react-doctor` skill instead.
How do I install it?
Run `npx skills add millionco/react-doctor --skill improve-react --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From millionco/react-doctor, a repository with 14,264 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.