사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
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
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" buildThe path: spec reads uncommitted React Doctor changes. Run RDE commands from the eval checkout.
Run a bounded sample
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.jsonIncrease --take only after tests and the first sample pass.
Inspect target-rule hits
For each hit, or a representative sample when counts are high:
- Open the pinned repository at the reported location.
- Compare the code with the rule contract.
- Classify the hit as true positive, false positive, or unsupported.
- Add a rule regression test for each false positive.
- Add confirmed false positives to the
fuzzregression corpus. - 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.
