millionco/react-doctor

rde-eval

Run a targeted local React Doctor Evals loop against an uncommitted rule change.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/millionco/react-doctor --skill rde-eval

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Run a local rule evaluation

Use React Doctor Evals (RDE) for bounded local iteration. Use run-parity only after the change has a pushed pull request.

Prepare both checkouts

sh
export REACT_DOCTOR_CHECKOUT=/absolute/path/to/react-doctor
export RDE_CHECKOUT=/absolute/path/to/react-doctor-evals

git -C "$RDE_CHECKOUT" pull --ff-only
ni -C "$RDE_CHECKOUT"
nr -C "$RDE_CHECKOUT" build
nr -C "$REACT_DOCTOR_CHECKOUT" build

The path: spec reads uncommitted React Doctor changes. Run RDE commands from the eval checkout.

Run a bounded sample

sh
cd "$RDE_CHECKOUT"
node dist/cli.js run "path:$REACT_DOCTOR_CHECKOUT" --runner local --take 100
node dist/cli.js digest "path:$REACT_DOCTOR_CHECKOUT" --rule <rule-id>
node dist/cli.js digest "path:$REACT_DOCTOR_CHECKOUT" --json --rule <rule-id> > <artifact-directory>/hits.json

Increase --take only after tests and the first sample pass.

Inspect target-rule hits

For each hit, or a representative sample when counts are high:

  1. Open the pinned repository at the reported location.
  2. Compare the code with the rule contract.
  3. Classify the hit as true positive, false positive, or unsupported.
  4. Add a rule regression test for each false positive.
  5. Add confirmed false positives to the fuzz regression corpus.
  6. Rebuild and rerun the same sample.

Record repository count separately from project-root count. Do not treat error records as clean scans.

Report results

Report checkout revisions, target rule, repositories, project roots, diagnostics, inspected hits, fixed false positives, and the artifact path. State any setup error or skipped repository.

After local validation, return to rule-validate. That skill decides whether to invoke pull request parity.

Related by task

from this repository

More skills

All skills
millionco
Community

react-doctor

Use when finishing a feature, fixing a bug, before committing React code, or when the user types /doctor, asks to scan, triage, or clean up React diagnostics. Covers lint, accessibility, bundle size, architecture. Includes a regression check and a full local-triage workflow that fetches the canonical playbook.

1h installs
2
GitHub stars
15.2K
Updated
Nov 20
millionco
Community

improve-threejs

Audit and fix Three.js and React Three Fiber apps for frame-loop performance, GPU memory leaks, scene-graph correctness, and visual defects like z-fighting, shadow acne, wrong color space, and broken resize handling. Uses React Doctor as the scanning engine plus a visual rubric checked against rendered output. Use when the user asks to improve, audit, scan, or clean up a Three.js, R3F, react-three-fiber, drei, or WebGL app, or types /improve-threejs.

1h installs
2
GitHub stars
15.2K
Updated
Nov 19
millionco
Community

rule-research

Define a precise React Doctor rule contract before implementation. Use when validating a rule idea, collecting official or open-source evidence, identifying false-positive traps, choosing detector precision, or setting first-version boundaries.

1h installs
1
GitHub stars
15.1K
Updated
Nov 7
millionco
Community

run-parity

Compare React Doctor diagnostics for a GitHub pull request (PR) with Vercel Sandbox. Use when asked to run parity, check a PR for diagnostic regressions, compare a PR with its base, or report added and removed diagnostics.

1h installs
1
GitHub stars
15.1K
Updated
Nov 7