42 lines
2.8 KiB
Text
42 lines
2.8 KiB
Text
Resolving dependencies
|
|
Resolved, downloaded and extracted [2]
|
|
|
|
Agent guidance
|
|
- Treat React Doctor diagnostics as starting hypotheses. Read the relevant code before confirming or suppressing each finding.
|
|
- For each group, decide true positive, false positive, or needs-human-review, then assign high/medium/low confidence.
|
|
- Do not suppress a finding without evidence from the file in question. Confidence requires code context.
|
|
- Understand the root cause before editing. Fix the underlying code instead of changing react-doctor config or suppressing rules unless explicitly asked.
|
|
- Investigate deeply where relevant: race conditions, security-sensitive flows, state propagation, multi-file refactors, and downstream dependency chains.
|
|
- Ignore pure style preferences, theoretical issues without real impact, missing features, and unrelated pre-existing code.
|
|
- Start with high-confidence fixes that preserve behavior. Leave low-confidence or product-dependent changes as notes.
|
|
- Run `npx react-doctor@latest --verbose --scope changed` before and after changes, plus relevant tests after each focused batch.
|
|
- When available, spawn subagents or isolated worktrees for independent rule families, then review and merge only the best safe fixes.
|
|
- Split unrelated, broad, or behavior-changing work into separate PRs/branches instead of one large cleanup.
|
|
- When one rule spans dozens of files (a migration-scale change), fix a representative sample first, confirm the recipe holds, and get the code owner's sign-off before changing the rest. Don't mass-fix a broad pattern in one unreviewed pass.
|
|
- For confirmed issues that cannot be fixed now, create GitHub issues with the rule, file/line, confidence, impact, and proposed fix.
|
|
- If a fix needs an API, UX, or architecture decision, stop and ask before editing.
|
|
|
|
✔ Scanned 1 file in 1.6s
|
|
|
|
React Doctor — symbuyote-info-site
|
|
Score disabled by --no-score. Want something custom to your company? Contact us at https://react.doctor/enterprise.
|
|
|
|
✔ No issues found!
|
|
Full diagnostics written to /var/folders/6t/3blzq7_j6p95xzry6t7c14hw0000gn/T/react-doctor-d169e412-3f40-45b4-8301-ca4f30855037
|
|
|
|
────────────────────────────────────────────────────────────
|
|
|
|
Docs: https://react.doctor/docs
|
|
Learn more about fixing issues, setting up CI/CD, and
|
|
configuring rules with a config file
|
|
|
|
GitHub: https://github.com/millionco/react-doctor
|
|
Report issues and star the repository!
|
|
|
|
|
|
React Doctor is not installed in this project.
|
|
Ask the user if they would like to set it up, then run:
|
|
|
|
npx react-doctor install --yes
|
|
|
|
This adds agent skill files, a `doctor` package script, and react-doctor as a dev dependency.
|