Get the React health scan to 100/100
Inventory every production React app, fix findings without suppressions, and prove a real 100/100 with full project checks.
Use this when
Use this for an authorized repository-wide React health pass when every production React app can be identified and a complete scan plus project checks can run locally.
How it runs
- Inventory the repository, production React app roots, current worktree state, and available validation commands.
- Run and record a full React Doctor baseline for every production app.
- Group findings by root cause and repair one coherent cause without weakening rules or changing unrelated behavior.
- Rerun the full scan and relevant typecheck, lint, tests, and builds, keeping only verified improvements.
- Escalate from symptom patches to ownership or data-flow analysis when a finding survives repeated repairs.
- Stop only at the success, blocked, approval-required, or no-progress state and return exact evidence.
Done when
✓ Every production React app has a genuine fresh 100/100 result. Record the React Doctor version, app roots, full final scan, and repository validation results; distinguish pre-existing failures and blockers from regressions caused by the repair work.
Why it works
A complete app inventory and fresh full scans prevent local or diff-only checks from masquerading as repository-wide health. Root-cause repair and anti-suppression rules make the final score evidence of better code rather than a configured-away problem.
Implementation note
Do not reset or overwrite unrelated work, disable findings, exclude files, relax severity, add unsafe casts or ignore directives, or delete meaningful behavior. Ask before breaking dependency upgrades or architectural changes outside the stated scope.
Source: Forward Future ↗graded C · 55/100 — how grades work →
More maintenance loops
Upgrade to current Node LTS
Move the project to the current Node LTS across .nvmrc, CI config, Dockerfiles, and engines, fixing deprecations until everything is green on the new runtime.
Upgrade dependencies one at a time
Walk through outdated dependencies one package per turn, upgrading, running the full check suite, and pinning back anything that breaks.
Triage untriaged issues to zero
Pick the oldest untriaged issue, validate it against the current build, then label it, close if obsolete, or document repro steps—one per turn until the queue empties or 12 iterations pass.