react-doctor
Run after making React changes to catch issues early. Use when reviewing code, finishing a feature, or fixing bugs in a React project.
70
Quality
63%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./config/claude/skills/react-doctor/SKILL.mdEvaluation results
100%
60%React Health Audit
Correct react-doctor command flags
Uses npx
0%
100%
npx -y flag
0%
100%
Uses @latest tag
0%
100%
Targets current directory
100%
100%
--verbose flag
100%
100%
--diff flag
0%
100%
Raw output captured
100%
100%
Without context: $0.5114 · 5m 19s · 31 turns · 34 in / 5,738 out tokens
With context: $0.4475 · 5m 19s · 26 turns · 34 in / 5,279 out tokens
95%
60%React Codebase Quality Improvement
Fix-then-verify workflow
Initial scan run
37%
100%
--verbose in both runs
0%
100%
--diff in both runs
0%
100%
Uses @latest
0%
100%
npx -y used
0%
100%
Errors fixed first
77%
72%
Follow-up scan run
46%
100%
Score comparison shown
64%
100%
Without context: $0.3871 · 2m 8s · 23 turns · 25 in / 6,655 out tokens
With context: $0.6467 · 6m 3s · 30 turns · 437 in / 9,594 out tokens
100%
81%Pre-Merge Code Review Check
Post-change diagnostic workflow
Uses npx
37%
100%
npx -y flag
0%
100%
Uses @latest
0%
100%
Targets dot
0%
100%
--verbose flag
0%
100%
--diff flag
0%
100%
Tool output included
80%
100%
Issues listed
100%
100%
Without context: $0.3615 · 4m 56s · 22 turns · 29 in / 5,049 out tokens
With context: $0.4439 · 4m 56s · 28 turns · 435 in / 5,251 out tokens
- Repository
- freekmurze/dotfiles
- Commit
355d067
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.