rde-eval
Run a targeted local React Doctor Evals loop against an uncommitted rule change. Use after focused rule tests pass, while inspecting real open-source hits, or when rule-validate needs local false-positive evidence before pull request parity.
Profile →npx skills add millionco/react-doctor --skill rde-eval --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.
# 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 e
- Prepare both checkouts
- Run a bounded sample
- Inspect target-rule hits
- Report results
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 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
What does the rde-eval skill do?
Run a targeted local React Doctor Evals loop against an uncommitted rule change. Use after focused rule tests pass, while inspecting real open-source hits, or when rule-validate needs local false-positive evidence before pull request parity.
How do I install it?
Run `npx skills add millionco/react-doctor --skill rde-eval --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.