react-analyzelisted
Install: claude install-skill riseshinee/superclaude-react
# react-analyze
Target: `$ARGUMENTS` (defaults to all of `src/`)
## Flags
| Flag | Meaning |
|---|---|
| `--focus <area>` | Analyze one area only. Without it, cover all areas shallowly |
| `--depth quick` | Heuristic grep-based scan of representative files (default) |
| `--depth deep` | File-by-file reading + parallel sub-agent analysis |
## Behavioral Flow
1. **Detect** — Confirm the stack with `react-stack`. Then get a fresh `react-map` and use it to locate code, following its token budget rules.
2. **Map** — Folder structure, route list, largest component files (top 10 by line count), dependency direction. The map's `## Routes` and `## Hotspots` sections cover most of this.
3. **Scan** — Use Grep with the checklist below to find candidates, then read those files to **confirm each issue is real**. Never report raw grep hits.
4. **Deep (optional)** — With `--depth deep`, delegate areas in parallel: architecture/performance→`react-architect`, security→`react-security`, test gaps→`react-qa`.
5. **Report** — Output in the format below.
## Checklist (detection signals by area)
**quality**
- Components over 300 lines, 10+ props, ternaries nested 3+ deep
- `any`, `as unknown as`, `@ts-ignore`, `eslint-disable`
- Duplicated fetch/formatting logic, dead code, unused exports
**architecture**
- Reverse-direction imports (shared → features, components → pages)
- Circular dependencies; barrel (`index.ts`) overuse causing huge imports
- Server data copied into global stores; prop