[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fAEI04VdyLOp4XjMXPq5JfkrvaY26RkzmqkqHidT_eVY":3},{"id":4,"publisher_id":5,"github_owner":6,"github_repo":7,"full_name":8,"description":9,"skill_count":10,"total_installs":11,"created_at":12,"stars":13,"external_total_installs":14,"external_total_installs_24h":15,"external_total_installs_updated_at":16,"publisher":17,"skills":24,"all_tags":63},"5228fc45-9fd4-49ef-80bb-0a81bee93b51","cb021b08-cb9f-4db1-9720-c9636f09e8c1","millionco","react-doctor","millionco/react-doctor","Diagnose and fix React codebase health issues. Use when reviewing React code, fixing performance problems, auditing security, or improving code quality.",1,0,"2026-02-20T20:48:20.340097+00:00",5860,11661,32,"2026-07-28T06:02:42.164+00:00",{"id":5,"bio":18,"name":19,"slug":6,"claimed":20,"verified":20,"avatar_url":21,"created_at":22,"github_type":23,"website_url":18,"github_login":6},null,"Million Software, Inc.",false,"https://avatars.githubusercontent.com/u/85101781?v=4","2026-02-20T20:48:20.123582+00:00","Organization",[25],{"id":26,"repo_id":4,"name":7,"description":27,"skill_id":7,"category_id":28,"content_md":29,"install_count":11,"install_count_24h":11,"verified":20,"created_at":30,"updated_at":31,"enabled":32,"last_resynced_at":33,"skill_md_path":34,"content_refreshed_at":31,"external_install_count":14,"external_install_count_24h":15,"external_install_count_updated_at":35,"content_hash":36,"search_summary":37,"trust_score":38,"risk_reason":18,"validated_at":39,"repo":40,"category":42,"tags":50,"publisher":61,"tools":62},"d9683ac4-d5da-427e-b35c-26051e1ef54e","Use when finishing a feature, fixing a bug, before committing React code, or when the user types `/doctor`, asks to scan, triage, or clean up React diagnostics. Covers lint, accessibility, bundle size, architecture. Includes a regression check and a full local-triage workflow that fetches the canonical playbook.","73e84002-7ccb-4f9a-bd3e-7f6dd68c6039","# React Doctor\n\nScans React codebases for security, performance, correctness, and architecture issues. Outputs a 0–100 health score.\n\n## After making React code changes:\n\nRun `npx react-doctor@latest --verbose --scope changed` and check the score did not regress.\n\nIf the score dropped, fix the regressions before committing.\n\n## For general cleanup or code improvement:\n\nRun `npx react-doctor@latest --verbose` (the default `--scope full`) to scan the full codebase. Fix issues by severity — errors first, then warnings.\n\n## For a focused UI design audit:\n\nRun `npx react-doctor@latest design --verbose`. This selects only design-tagged UI composition, typography, interaction, accessibility, and motion rules, including focused rules that remain opt-in during a general health scan.\n\n## /doctor — full local triage workflow\n\nWhen the user types `/doctor`, says \"run react doctor\", or asks for a full triage / cleanup pass (not just a regression check), fetch the canonical local-triage playbook and follow every step in it:\n\n```bash\ncurl --fail --silent --show-error \\\n  --header 'Cache-Control: no-cache' \\\n  https://www.react.doctor/prompts/react-doctor-agent.md\n```\n\nThe playbook is the single source of truth — a scan → filter → triage → fix → validate loop that edits the working tree directly (never commits, never opens PRs). Updating the prompt at its source updates every agent on its next fetch — no skill reinstall needed.\n\nPair it with the matching per-rule prompts at `https://www.react.doctor/prompts/rules/\u003Cplugin>/\u003Crule>.md` (fetched on demand inside the playbook) so each fix uses the canonical, reviewer-tested recipe.\n\n## Configuring or explaining rules\n\nWhen the user wants to understand a rule, disagrees with one, or wants to disable / tune which rules run (not fix code), read [references/explain.md](references/explain.md) and follow it. Start with `npx react-doctor@latest rules explain \u003Crule>`, then apply the narrowest control via `npx react-doctor@latest rules disable|set|category|ignore-tag …`, which edits your `doctor.config.*` (or `package.json#reactDoctor`).\n\n## Command\n\n```bash\nnpx react-doctor@latest --verbose --scope changed\n```\n\n| Flag              | Purpose                                                          |\n| ----------------- | ---------------------------------------------------------------- |\n| `.`               | Scan current directory                                           |\n| `--verbose`       | Show affected files and line numbers per rule                    |\n| `--scope changed` | Only report issues introduced vs the base branch (default: full) |\n| `--scope lines`   | Only report issues on the changed lines                          |\n| `--score`         | Output only the numeric score                                    |\n| `design`          | Run only the focused UI design diagnostics                       |","2026-02-20T20:48:22.505813+00:00","2026-07-28T04:06:36.077+00:00",true,"2026-07-08T05:02:36.705+00:00","skills/react-doctor/SKILL.md","2026-07-28T06:02:18.449+00:00","f01d6ac4f37a3a13f2c060e3d35ae479416721c11851c8473540f28bd597c0ee","React Doctor is a CLI tool for React developers to scan and triage React codebases for security, performance, lint, accessibility, bundle size, and architecture issues. It supports workflows like pre-commit regression checks on changed code and full codebase triage with automated fixing using a canonical prompt playbook. This skill targets React projects and helps ensure code health by providing a 0–100 score and orchestrating fixes without committing changes, suitable for maintaining React app code quality and reliability.",90,"2026-06-16T04:02:16.91+00:00",{"id":4,"stars":13,"full_name":8,"publisher":41,"created_at":12,"description":9,"github_repo":7,"skill_count":10,"github_owner":6,"publisher_id":5,"total_installs":11,"external_total_installs":14,"external_total_installs_24h":15,"external_total_installs_updated_at":16},{"id":5,"bio":18,"name":19,"slug":6,"claimed":20,"verified":20,"avatar_url":21,"created_at":22,"github_type":23,"website_url":18,"github_login":6},{"id":28,"icon":43,"name":44,"slug":45,"intent":46,"reason":47,"sort_order":48,"description":49},"🚀","Test, Deploy & Monitor","test-deploy-monitor","I need to ship quality code and keep it running","Place a skill here when its primary purpose is QUALITY ASSURANCE, DEPLOYMENT, or OPERATIONAL RELIABILITY of code. This includes: end-to-end testing (Playwright, Cypress), unit and integration testing (Vitest, Mocha, PHPUnit), test-driven development workflows, CI/CD pipeline setup and automation, deployment to hosting platforms (Vercel, Shopify, production servers), code review processes and pull request analysis, debugging tools and systematic debugging methodologies, development environment setup (local dev, Docker, Vagrant), code quality auditing (linting, static analysis, SonarQube), component documentation generation, platform diagnostics and troubleshooting (Magento diagnostics, Shopify debugging). KEY DISTINCTION: This is about the DEVELOPMENT LIFECYCLE — writing tests, deploying, debugging, reviewing. If the skill teaches testing best practices as a methodology → 'Learn & Follow Best Practices'. If it measures site speed → 'Optimize Speed & Performance'. If it monitors production errors → this category (it's operational reliability).",12,"Playwright, CI/CD, Docker, debugging, code review — the dev lifecycle from local to production.",[51,56],{"id":52,"name":53,"slug":53,"color":54,"enabled":32,"created_at":55,"is_keyword":20,"claimed":20},"776bb7e8-a2a0-4315-9cab-9665ae82fd2d","performance","#eab308","2026-02-01T21:22:12.639775+00:00",{"id":57,"name":58,"slug":58,"color":59,"enabled":32,"created_at":60,"is_keyword":20,"claimed":20},"82b5382f-0c99-4515-b952-848ee9ac03c1","react","#22c55e","2026-02-04T19:32:18.578582+00:00",{"id":5,"bio":18,"name":19,"slug":6,"claimed":20,"verified":20,"avatar_url":21,"created_at":22,"github_type":23,"website_url":18,"github_login":6},[],[64,65],{"id":52,"name":53,"slug":53,"color":54,"enabled":32,"created_at":55,"is_keyword":20,"claimed":20},{"id":57,"name":58,"slug":58,"color":59,"enabled":32,"created_at":60,"is_keyword":20,"claimed":20}]