cleanup · superclaude-org — Claude Code command: what it does, how to install
The cleanup command for Claude Code finds dead code, removes unused imports, and tidies project structure without breaking public APIs.
MIT ★ 23,950 updated 2026-09-27
.claude/commands/cleanup.mdWhat cleanup does
The command works through a structured five-stage cycle: analyze targets, pick specialized personas, execute cleanups, test for regressions, and deliver a final summary. Unused imports, empty blocks, and symbols lacking any references get cleared automatically. Whenever an item touches external exports, test utilities, or configuration values, the tool pauses and requests explicit approval.
Execution relies on standard file tools like Read, Grep, Glob, and MultiEdit, tracking multi-file jobs via TodoWrite. If configured, sequential and context7 MCP servers supply step-by-step dependency reasoning and framework patterns; missing servers trigger a graceful switch to native model logic and web documentation.
What it helps with
- strip unused imports and redundant type annotations
- detect and purge zero-reference dead code
- reorganize project files while validating dependencies
Example prompts for the agent
- /sc:cleanup src/ --type code --safe
- /sc:cleanup --type imports --preview
- /sc:cleanup --type all --interactive
How to install cleanup
Manually: put the files in place
.claude/commands/cleanup.mdCall it with /cleanup. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/cleanup.mdCall it with /prompts:cleanup. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/cleanup.prompt.mdManually: put the files in place
.gemini/commands/cleanup.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about cleanup
How to install cleanup in Claude Code?
Place the command specification file into .claude/commands/cleanup.md.
What does cleanup do?
It discovers unreachable code, removes orphaned imports, and reorganizes project structures while guarding against regressions.
Are sequential and context7 MCP servers mandatory?
No, they act as preferred tooling: the workflow automatically falls back to native model reasoning and web search if either server is absent.
Source text
cleanup.md · MIT
--- name: cleanup description: "Systematically clean up code, remove dead code, and optimize project structure" category: workflow complexity: standard mcp-servers: [sequential, context7] personas: [architect, quality, security] --- # /sc:cleanup - Code and Project Cleanup ## Triggers - Code maintenance and technical debt reduction requests - Dead code removal and import optimization needs - Project structure improvement and organization requirements - Codebase hygiene and quality improvement initiatives ## Usage ``` /sc:cleanup [target] [--type code|imports|files|all] [--safe|--aggressive] [--interactive] ``` ## Behavioral Flow 1. **Analyze**: Assess cleanup opportunities and safety considerations across target scope 2. **Plan**: Choose cleanup approach and activate relevant personas for domain expertise 3. **Execute**: Apply systematic cleanup with intelligent dead code detection and removal 4. **Validate**: Ensure no functionality loss through testing and safety verification 5. **Report**: Generate cleanup summary with recommendations for ongoing maintenance Key behaviors: - Multi-persona coordination (architect, quality, security) based on cleanup type - Framework-specific cleanup patterns via Context7 MCP integration - Systematic analysis via Sequential MCP for complex cleanup operations - Safety-first approach with backup and rollback capabilities ## MCP Integration - **Sequential MCP**: Auto-activated for complex multi-step cleanup analysis and planning - **Context7 MCP**: Framework-specific cleanup patterns and best practices - **Persona Coordination**: Architect (structure), Quality (debt), Security (credentials) - **Availability fallback**: The MCP servers named here are preferred tooling, not hard requirements — when one is not installed, degrade gracefully (native reasoning in place of Sequential, official docs via web lookup in place of Context7, native tools otherwise) instead of routing work to absent servers. ## Tool Coordination - **Read/Grep/Glob**: Code analysis and pattern detection for cleanup opportunities - **Edit/MultiEdit**: Safe code modification and structure optimization - **TodoWrite**: Progress tracking for complex multi-file cleanup operations - **Task**: Delegation for large-scale cleanup workflows requiring systematic coordination ## Key Patterns - **Dead Code Detection**: Usage analysis → safe removal with dependency validation - **Import Optimization**: Dependency analysis → unused import removal and organization - **Structure Cleanup**: Architectural analysis → file organization and modular improvements - **Safety Validation**: Pre/during/post checks → preserve functionality throughout cleanup ## Examples ### Safe Code Cleanup ``` /sc:cleanup src/ --type code --safe # Conservative cleanup with automatic safety validation # Removes dead code while preserving all functionality ``` ### Import Optimization ``` /sc:cleanup --type imports --preview # Analyzes and shows unused import cleanup without execution # Framework-aware optimization via Context7 patterns ``` ### Comprehensive Project Cleanup ``` /sc:cleanup --type all --interactive # Multi-domain cleanup with user guidance for complex decisions # Activates all personas for comprehensive analysis ``` ### Framework-Specific Cleanup ``` /sc:cleanup components/ --aggressive # Thorough cleanup with Context7 framework patterns # Sequential analysis for complex dependency management ``` ## Boundaries **Will:** - Systematically clean code, remove dead code, and optimize project structure - Provide comprehensive safety validation with backup and rollback capabilities - Apply intelligent cleanup algorithms with framework-specific pattern recognition **Will Not:** - Remove code without thorough safety analysis and validation - Override project-specific cleanup exclusions or architectural constraints - Apply cleanup operations that compromise functionality or introduce bugs ## AUTO-FIX VS APPROVAL-REQUIRED **Auto-fix (applies automatically)**: - Unused imports removal - Dead code with zero references - Empty blocks removal - Redundant type annotations **Approval Required (prompts user first)**: - Code with indirect references - Exports potentially used externally - Test fixtures/utilities - Configuration values **Safety Threshold**: - If code has ANY usage path, prompt user - If code affects public API, prompt user - If unsure, prompt user
© SuperClaude-Org · MIT · SuperClaude-Org/SuperClaude_Framework
Similar slash commands
All slash commands for Code review and refactoring →cleanup by other authors comes first.