react-doctor
Diagnose and health-check the React frontend codebase using react-doctor. Use when reviewing frontend code, fixing React performance issues, or verifying component best practices.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- react-doctor
- description
- Diagnose and health-check the React frontend codebase using react-doctor. Use when reviewing frontend code, fixing React performance issues, or verifying component best practices.
03 SKILL.md 正文
React doctor skill
Use react-doctor to analyze the React frontend application for common performance bottlenecks, anti-patterns, and component health issues.
When to run
- Before finalizing major React component changes or refactors.
- When investigating frontend performance regressions, unexpected re-renders, or memory leaks.
- As part of periodic frontend code quality reviews.
How to run
From the frontend/ directory:
cd frontend && npm run doctor
Interpreting results and acting on findings
- Re-render warnings: Check component memoization (
useMemo,useCallback) and object/array reference stability in props. - Hook usage rules: Verify hook dependency arrays and ensure hooks are called unconditionally at the top level.
- State management: Avoid redundant state that can be derived during rendering.
- Action: Apply targeted code fixes to address reported issues, re-run
npm run doctor, and confirm warnings are resolved.
04 同仓库更多 Skills
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
to-tickets
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
to-spec
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.