| name | source-command-sc-cleanup |
| description | Systematically clean up code, remove dead code, and optimize project structure |
source-command-sc-cleanup
Use this skill when the user asks to run the migrated source command sc-cleanup.
Command Template
/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
- Analyze: Assess cleanup opportunities and safety considerations across target scope
- Plan: Choose cleanup approach and activate relevant personas for domain expertise
- Execute: Apply systematic cleanup with intelligent dead code detection and removal
- Validate: Ensure no functionality loss through testing and safety verification
- 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)
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
