rule-validate
Validate an implemented React Doctor rule before merge. Use after focused tests pass to review detector correctness, inspect open-source hits, run pull request parity, add regression coverage, prepare a changeset, write pull request copy, or address review findings.
Profile →npx skills add millionco/react-doctor --skill rule-validate --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.
# Validate a rule Verify that the implementation matches its `rule-research` contract on tests and real code. ## Review the implementation Check for: - false positives and missed claimed behavior - incorrect imports, aliases, or shadowed bindings - impossible control-flow path merges - nested functions treated as immediate execution - dynamic properties treated as static names - missed transparent wrappers - unsupported imported values - messages that overstate detection - missing valid and invalid tests Use `truffler` before accepting a new helper: ```sh bunx @rayhanadev/truffler "<helper-name>" packages \ --kind function,method,interface,type,constant --limit 20 ``` Fix each implementation bug with a focused regression test. ## Run validation Run focused tests, package typecheck, and required lint and format checks. Run broader checks when the change affects shared behavior. Use `rde-eval` for bounded local inspection of the target rule. Inspect all hits when counts are low and a representative sample when counts are high. Add every confirmed false positive to rule tests and the `fuzz` corpus. Run `run-parity` for every new rule or detector behavior change after the pull request
- Review the implementation
- Run validation
- Prepare release artifacts
- Handle review findings
- Report validation
bunx @rayhanadev/truffler "<helper-name>" packages \
What does the rule-validate skill do?
Validate an implemented React Doctor rule before merge. Use after focused tests pass to review detector correctness, inspect open-source hits, run pull request parity, add regression coverage, prepare a changeset, write pull request copy, or address review findings.
How do I install it?
Run `npx skills add millionco/react-doctor --skill rule-validate --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.