The React Doctor 100/100 loop

An AI coding-agent workflow for inventorying every production React app, fixing React Doctor findings without suppression, and proving a genuine 100/100 result with full project checks.

Use 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.

The loop

Bring every production React app in [repository] to a freshly verified React Doctor score of 100/100. Inventory app roots, record a full `npx react-doctor@latest --verbose` baseline, fix one root cause at a time, and rerun the full scan plus relevant typecheck, lint, tests, and builds. Never hide findings with exclusions, ignores, suppressions, deleted behavior, or relaxed rules. Stop at 100/100 for every app, blocked, approval-required, or no measurable progress; preserve unrelated work and report exact proof.

Steps

• 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.

Verification

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.