| name | cleanup |
| description | Run all code quality skills — effects, memo, callbacks, state, React Query, emcn design review, url-state, and comments — analyzing in parallel, then applying fixes sequentially |
| argument-hint | [scope] [fix=true|false] |
Cleanup
Arguments:
- scope: what to review (default: your current changes). Examples: "diff to main", "PR #123", "src/components/", "whole codebase"
- fix: whether to apply fixes (default: true). Set to false to only propose changes.
User arguments: $ARGUMENTS
Step 1 — Parallel analysis (read-only)
First parse the user's $ARGUMENTS into scope and fix: extract the fix=true|false token wherever it appears in the string (start, middle, or end), and treat everything else — with that token removed — as scope. Defaults: scope = your current changes, fix = true. The fix value is consumed by Step 3 — it does NOT propagate to these passes, which always run fix=false.
Spawn all eight passes concurrently as subagents in a single message (multiple Agent tool calls). Each runs its skill on the parsed scope with fix=false — analysis and proposals ONLY, no edits. Instruct each agent to return its findings as a structured list: for every proposed change, the file path, line range, a one-line description of the change, and the exact before/after so the orchestrator can apply it without re-deriving.
Run these eight in parallel, substituting the parsed scope for in each invocation (pass the real scope text, never the literal ):
