millionco/react-doctor

rde-eval

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

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/millionco/react-doctor --skill rde-eval

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

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.

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
millionco
コミュニティ

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.

1時間の導入数
2
GitHub Stars
1.5万
更新日
11月20日
millionco
コミュニティ

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.

1時間の導入数
2
GitHub Stars
1.5万
更新日
11月19日
millionco
コミュニティ

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.

1時間の導入数
1
GitHub Stars
1.5万
更新日
11月7日
millionco
コミュニティ

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.

1時間の導入数
1
GitHub Stars
1.5万
更新日
11月7日