react-doctor

Estrellas4

Forks0

Actualizado13 de mayo de 2026 a las 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.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

yehezkieldio

yehezkieldio/portfolio

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de garantía de calidad de software y probadoresOcupaciones informáticas y matemáticas·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

Más de este repositorio

mismo repositorio

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