Run any Skill in Manus with one click

react-doctor

Stars4

Forks0

UpdatedMay 13, 2026 at 20:15

Use when finishing a feature, fixing a bug, before committing React code, or when the user wants to improve code quality or clean up a codebase. Checks for score regression. Covers lint, dead code, accessibility, bundle size, architecture diagnostics.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

yehezkieldio

yehezkieldio/portfolio

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	react-doctor
description	Use when finishing a feature, fixing a bug, before committing React code, or when the user wants to improve code quality or clean up a codebase. Checks for score regression. Covers lint, dead code, accessibility, bundle size, architecture diagnostics.
version	1.0.0

React Doctor

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

After making React code changes:

Run bunx -y react-doctor@latest . --verbose --diff and check the score did not regress.

If the score dropped, fix the regressions before committing.

For general cleanup or code improvement:

Run bunx -y react-doctor@latest . --verbose (without --diff) to scan the full codebase. Fix issues by severity — errors first, then warnings.

Command

bunx -y react-doctor@latest . --verbose --diff

Flag	Purpose
`.`	Scan current directory
`--verbose`	Show affected files and line numbers per rule
`--diff`	Only scan changed files vs base branch
`--score`	Output only the numeric score

More from this repository

same repository

design-engineer

yehezkieldio/portfolio

Build interfaces with design engineering craft — the intersection of design and code. Use this skill when the user asks to build UI components, interactive elements, animations, micro-interactions, or polished web experiences. Triggers on mentions of "design engineer", "interaction design", "micro-interactions", "craft", "polish", "delight", "animation", "motion design", "haptics", "toast", "command palette", "design system components", or requests for interfaces that feel alive, responsive, and meticulously detailed. This skill should also be used when the user wants to add invisible details, fine-tune interactions, or make something "feel right". Complements the frontend-design skill by focusing specifically on interaction quality, motion, and engineering craft.

2026-05-054

name	react-doctor
description	Use when finishing a feature, fixing a bug, before committing React code, or when the user wants to improve code quality or clean up a codebase. Checks for score regression. Covers lint, dead code, accessibility, bundle size, architecture diagnostics.
version	1.0.0

React Doctor

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

After making React code changes:

Run bunx -y react-doctor@latest . --verbose --diff and check the score did not regress.

If the score dropped, fix the regressions before committing.

For general cleanup or code improvement:

Run bunx -y react-doctor@latest . --verbose (without --diff) to scan the full codebase. Fix issues by severity — errors first, then warnings.

Command

bunx -y react-doctor@latest . --verbose --diff

Flag	Purpose
`.`	Scan current directory
`--verbose`	Show affected files and line numbers per rule
`--diff`	Only scan changed files vs base branch
`--score`	Output only the numeric score