improve-react

Audits React codebases and writes prioritized, self-contained implementation plans for other agents.

1|Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Chia1104/agent-air --skill improve-react-chia1104
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: improve-react
Source: https://github.com/Chia1104/agent-air/tree/main/skills/shared/improve-react
Command: npx skills add https://github.com/Chia1104/agent-air --skill improve-react-chia1104

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires react-doctor.

What problem does it solve? React codebases accumulate subtle bugs, performance regressions, and accessibility gaps that static scanners list without judgment. This Skill turns React Doctor's raw scan output into a senior-engineer audit: it decides which findings actually matter, prioritizes them by user impact, and writes plans precise enough for a cheaper model to execute without context. ## Core Features & Use Cases - Evidence-based audit: Runs React Doctor read-only as JSON, then vets every finding at its file:line against five categories — bugs, performance, accessibility, security, and maintainability. - Leverage-driven prioritization: Severity is judged by hot-path impact (per-keystroke components, provider fan-out, untrusted-input sinks), not the rule's raw severity. - Self-contained plans: Each plan inlines the exact current code, the canonical fix recipe from react.doctor, repo conventions, scope boundaries, and mechanical plus behavioral verification steps. - Use Case: Ask it to audit a Next.js app before a performance push; it scans, confirms the unstable context value re-rendering the whole tree, and writes a plan another agent executes in an isolated worktree. ## Quick Start Ask the agent 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, vets each finding at its file:line, and prioritizes by user impact. It outputs a severity-ranked table across bugs, performance, accessibility, security, and maintainability, then writes executable plans.

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 leverage judgment, and writes plans that other agents or cheaper models execute later.

Does improve-react modify my source code?▼

No. It never edits source, runs no --fix, and makes no commits. The only files it creates live under plans/ (or react-plans/ if plans/ is taken); execution happens separately via improve-react execute or any agent running the plan.

Can I audit only one category like accessibility or security?▼

Yes. Invoke it with a category focus such as performance, accessibility, security, bugs, or maintainability to run recon and audit that category only. You can also use quick or deep to adjust audit effort and subagent count.

When should I not use improve-react?▼

Skip it for regression checks or fix-it-now passes on a single diff — use the react-doctor skill instead. It is designed for whole-codebase surveys and roadmaps of fixes, not immediate in-place repairs.