Menu
Technical debt and refactoring — analyze, refactor, and validate code improvements
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Build and deploy features — branch, implement, commit, review, test, deploy, PR/merge
shadcn/ui component patterns including Radix UI primitives, CVA variants, form components with React Hook Form, and Tailwind CSS styling. Use when creating UI components, building forms, implementing design systems, or working with shadcn/ui.
Add critical test coverage — tests ONLY for functionality that could cause production disasters
List all available tools with their signatures and purposes
Analyze Claude Code audit logs — session summaries, metrics, timelines, anomaly detection, and claim verification
Create a new custom agent using the meta-agent with guided requirements gathering
| name | team-cleanup |
| description | Technical debt and refactoring — analyze, refactor, and validate code improvements |
| argument-hint | <area or module to clean up> |
| disable-model-invocation | true |
| allowed-tools | Bash(git *), TaskCreate, TaskUpdate, TaskList, TaskGet |
Improve code quality, performance, and maintainability through targeted refactoring.
Area to clean up: $ARGUMENTS
Enable with CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1
Create a team and spawn teammates:
cleanup-<area-slug>Create the following task list with dependencies:
| # | Task | Owner | Blocked By |
|---|---|---|---|
| 1 | Create branch refactor/<area> from main | shipper | — |
| 2 | Analyze code for smells, bottlenecks, and refactoring opportunities | reviewer | 1 |
| 3 | Refactor application code based on review findings | full-stack-developer | 2 |
| 4 | Refactor data layer based on review findings (if needed) | database-admin | 2 |
| 5 | Commit refactoring changes | shipper | 3, 4 |
| 6 | Run full test suite and validate | shipper | 5 |
| 7 | Update documentation for refactoring changes | documentor | 6 |
| 8 | Create PR to main with before/after summary | shipper | 6, 7 |
Parallelism: Tasks 3 and 4 can run simultaneously after the review completes.
Execute sequentially using the Task tool:
Task(shipper, "Create branch refactor/<area> from main")Task(reviewer, "Analyze $ARGUMENTS for code smells, bottlenecks, refactoring opportunities")Task(full-stack-developer, "Refactor based on review findings: <findings>")Task(database-admin, "Refactor data layer: <findings>") — only if neededTask(shipper, "Commit changes: refactor: <description>")Task(shipper, "Run full test suite, validate no regressions")Task(documentor, "Update docs for refactoring changes in: $ARGUMENTS")Task(shipper, "Create PR to main with before/after summary")┌─────────┐ ┌──────────┐ ┌──────────────────┐ ┌─────────┐ ┌─────────┐ ┌────────────┐ ┌─────────┐
│ Shipper │────►│ Reviewer │────►│ Full Stack Dev │────►│ Shipper │────►│ Shipper │────►│ Documentor │────►│ Shipper │
│ Branch │ │ Analyze │ │ + DB Admin (||) │ │ Commit │ │ Test │ │ Update Docs│ │ PR │
└─────────┘ └──────────┘ │ Refactor │ └─────────┘ └─────────┘ └────────────┘ └─────────┘
│ └──────────────────┘
[Identify Issues]
[Prioritize]