improve-react

Audits React codebases and generates prioritized, self-contained implementation plans from React Doctor scan evidence.

3|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/langgenius/due-date-hq-jwl --skill improve-react-langgenius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: improve-react
Source: https://github.com/langgenius/due-date-hq-jwl/tree/main/.claude/skills/improve-react
Command: npx skills add https://github.com/langgenius/due-date-hq-jwl --skill improve-react-langgenius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires react-doctor.

What problem does it solve? React codebases accumulate subtle bugs, performance regressions, accessibility gaps, and security risks that static scanners flag without judgment. This Skill turns React Doctor scan output into a senior-engineer audit: it vets which findings actually matter, prioritizes them by user impact, and writes implementation plans precise enough for any agent or cheaper model to execute without further judgment calls. ## Core Features & Use Cases - Evidence-based audit: Runs React Doctor read-only as JSON, then audits across five categories (bugs & correctness, performance, accessibility, security, maintainability) with parallel subagents. - Leverage-driven prioritization: Severity is judged by hot-path impact, not raw rule severity, and findings are confirmed at their exact file:line before being reported. - Self-contained plans: Each plan inlines the current code, the exact target fix pulled from the canonical per-rule prompt at react.doctor, repo conventions, boundaries, and verification steps including React DevTools Profiler checks. - Use Case: Ask it to audit a Next.js app before a release; it produces a vetted findings table plus a plans/ directory of numbered, commit-stamped plans that a cheaper executor agent can implement one by one. ## Quick Start Ask the assistant to audit this React codebase and produce prioritized improvement plans using the improve-react skill.

Frequently Asked Questions about improve-react

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a React codebase for performance and bugs?

Run the improve-react skill, which executes React Doctor read-only as JSON, then audits findings across five categories with parallel subagents. It confirms each finding at its file:line and outputs a prioritized table ordered by user-impact leverage.

What is the difference between improve-react and react-doctor?

react-doctor runs the scanner and fixes the working tree directly via its /doctor flow. improve-react is read-only: it uses the scan as evidence, adds senior-engineer judgment on what matters, and writes plans for other agents to execute later.

Does improve-react modify my source code?

No. It never edits source files, runs formatters, installs dependencies, or commits. The only files it creates are plan documents under plans/ (or react-plans/ if plans/ is taken); execution is delegated to a separate agent or the react-doctor skill.

Can I audit only one category like accessibility or security?

Yes. Pass a category focus such as performance, accessibility, security, bugs, or maintainability, and the skill runs recon plus an audit of that category only. You can also use quick or deep to adjust audit effort and subagent count.

Why does improve-react fetch fix recipes from react.doctor?

React Doctor publishes a reviewer-tested canonical fix prompt for every rule at react.doctor/prompts/rules/<plugin>/<rule>.md. Plans must inline that exact recipe rather than approximate a fix, so executors with zero context apply the verified solution.

When should I not use improve-react?

Skip it for single-diff reviews, regression checks, or fix-it-now passes; use the react-doctor skill instead. It is designed for whole-codebase audits and roadmap-style planning, not immediate in-place fixes.