Index of every page on this site: llms.txt
All skills
millionco avatar

/react-doctor

@b6ba66e
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/millionco/react-doctor/react-doctor

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈82 tokens for metadata: the name and description. ≈1.4k when used: this file. ≈1.4k more on demand in 1 file.

Description uses 4.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈328 characters, or 4.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

React Doctor

Scans React codebases for security, performance, correctness, and architecture issues. Outputs a 0–100 health score.

After making React code changes:

Run npx react-doctor@latest --verbose --scope changed and check the score did not regress.

If the score dropped, fix the regressions before committing.

For general cleanup or code improvement:

Run npx react-doctor@latest --verbose (the default --scope full) to scan the full codebase. Fix issues by severity — errors first, then warnings.

For a focused UI design audit:

Run 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.

For runtime performance problems:

Run npx react-doctor@latest scan <url> --format json in an interactive terminal. React Doctor opens an isolated system Chrome profile, records a DevTools trace while the user reproduces the slow interaction, and flashes purple outlines with component names as React renders. It stops when they press Enter. Read the structured summary first, then inspect the returned local .json.gz trace for CPU, browser, and React component evidence.

If the user needs their authenticated browser state, use --cdp <remote-debugging-url>. This requires Chrome to already be running with remote debugging. Never ask for cookies or copy the user's browser profile. Treat the trace as sensitive local application data and never upload it without explicit permission.

/doctor — full local triage workflow

When 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:

curl --fail --silent --show-error \
  --header 'Cache-Control: no-cache' \
  https://www.react.doctor/prompts/react-doctor-agent.md

The 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.

Pair it with the matching per-rule prompts at https://www.react.doctor/prompts/rules/<plugin>/<rule>.md (fetched on demand inside the playbook) so each fix uses the canonical, reviewer-tested recipe.

Use --scope contextual --base origin/main when a team wants existing findings in the code it is editing. Rules can select an element, function, file, or an explicit set of related nodes. For exhaustive-deps, edits in the hook call or a resolved local callback can surface a finding on an unchanged dependency array. Rules without wider ownership keep changed-line filtering.

Configuring or explaining rules

When 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 and follow it. Start with npx react-doctor@latest rules explain <rule>, 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).

Command

npx react-doctor@latest --verbose --scope changed
Flag Purpose
. Scan current directory
--verbose Show affected files and line numbers per rule
--scope changed Only report issues introduced vs the base branch (default: full)
--scope contextual Report findings in modified functions, JSX elements, or files, as selected by each rule
--scope lines Only report issues on the changed lines
--score Output only the numeric score
design Run only the focused UI design diagnostics

Reuse a base scan

Save a complete --json scan, then pass --baseline base-report.json to report only new findings. This also works with --scope changed. Use the same version and rules for both scans. Findings are grouped by rule and file path, following Git renames. Only increases in each group's count are reported; groups without an increase skip location matching. Fingerprints, message similarity, and Git-adjusted line distance select the added findings. Formatting and edits that keep the same counts report no new findings. Saved reports must use the same textComponents, rawTextWrapperComponents, and respectInlineDisables settings. Regenerate the base report after changing these settings, or use a Git comparison. Older reports without fingerprints or sourceFilterConfigHash must be regenerated.

GitLab warning status

For GitLab CI, --warning-exit-code 123 returns 123 for non-blocking warnings. Pair it with allow_failure: { exit_codes: 123 }. Errors still return 1. Accepts integers from 2 to 255. --blocking warning still returns 1. --blocking none or --score skips this warning signal.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 alert2d5 checks · Risk SAFE
  • Gen Agent Trust Hub3d

    The skill is generally safe and adheres to secure practices for handling browser trace data. It downloads diagnostic tools and fetches agent 'playbooks' (instructions) from the vendor's website at runtime to manage its workflow. This creates a surface for indirect prompt injection, as the agent is instructed to follow instructions fetched from a remote URL.

  • Socket2d

    No alerts

  • Snyk3d

    Risk: CRITICAL · 2 issues

  • Runlayer8mo

    1 file scanned · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at b6ba66e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated last month
version
1.2.0

README badge

README badge for millionco/react-doctor

Scans React codebases for security, performance, correctness, and architecture issues, outputting a 0–100 health score. Use before committing to catch regressions, or run the full `/doctor` workflow to triage and fix issues by severity across the entire codebase.

Generated from the current SKILL.md.

Does this work with Next.js or other React frameworks?
React Doctor scans React codebases generally. The SKILL.md does not specify framework-specific limitations, so it should work with Next.js, Remix, and similar React-based projects, though the scope of checks may vary.
What categories of issues does react-doctor check for?
It scans for security, performance, correctness, and architecture issues. It also covers linting, accessibility, and bundle size concerns.
Can I check only the code I just changed instead of the full codebase?
Yes. Use `--scope changed` to report only issues introduced vs the base branch, or `--scope lines` to report only issues on the changed lines themselves.
Can I disable or customize which rules run?
Yes. Use `npx react-doctor@latest rules disable|set|category|ignore-tag` to control which rules apply, and the configuration is stored in `doctor.config.*` or `package.json#reactDoctor`.
Does the skill update automatically, or do I need to reinstall it?
The canonical playbook and per-rule prompts are fetched from react.doctor on demand, so updates to the source prompt apply automatically on the next fetch without skill reinstall.

Generated from the current SKILL.md. These answers refresh after source changes.