About this Skill
Records a selected interaction with React Doctor, connects trace evidence to source, and compares repeat measurements after a fix.
Why we picked it
Source-based listing; the workflow was reviewed from upstream documentation and was not run for this listing.
What it helps with
- Diagnose a reproducible React interaction with browser traces, rendering evidence and a structured report.
How to use it
Records a selected interaction with React Doctor, connects trace evidence to source, and compares repeat measurements after a fix.
License and data use
The upstream CLI reports anonymous usage and crashes by default; consult its data-use policy. The CLI documents --no-telemetry as an opt-out.
The repository uses a modified MIT license with additional restrictions on AI training/evaluation and paid hosted offerings; read the full license.
Before you use it
- A coding agent with access to the target project. React Doctor scans require Node.js ^20.19.0 or >=22.13.0 and package access.
- The upstream CLI reports anonymous usage and crashes by default; consult its data-use policy. The CLI documents --no-telemetry as an opt-out.
- The repository uses a modified MIT license with additional restrictions on AI training/evaluation and paid hosted offerings; read the full license.
- Runtime traces need Chrome and an interactive session. Trace files may contain application URLs and behavior; keep them local unless authorized.
Supported agents
Sources & references
Original sources are linked below. Practical starting points are editorial suggestions from SkillHey.
