Files
SuperClaude/.claude/commands/cleanup.md
NomenAK bce31d52a8 Initial commit: SuperClaude v4.0.0 configuration framework
- Core configuration files (CLAUDE.md, RULES.md, PERSONAS.md, MCP.md)
- 17 slash commands for specialized workflows
- 25 shared YAML resources for advanced configurations
- Installation script for global deployment
- 9 cognitive personas for specialized thinking modes
- MCP integration patterns for intelligent tool usage
- Token economy and ultracompressed mode support

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-06-22 14:02:49 +02:00

2.3 KiB

Legend

Symbol Meaning Abbrev Meaning
leads to cfg configuration
& and/with deps dependencies
w/ with perf performance

Execute immediately. Add --plan flag if user wants to see plan first.

Clean up project artifacts, code & cfg specified in $ARGUMENTS.

--code flag:

  • Remove unused imports & dead code | Clean console.log & debug code
  • Remove commented blocks | Fix style inconsistencies | Remove TODO>30 days

--files flag:

  • Remove build artifacts & temp files | Clean node_modules if corrupted
  • Remove logs & cache dirs | Clean test outputs | Remove OS files (.DS_Store, thumbs.db)

--deps flag:

  • Remove unused deps from package.json | Update vulnerable deps
  • Clean duplicate deps | Optimize dep tree | Check outdated packages

--git flag:

  • Remove untracked files (w/ confirmation) | Clean merged branches
  • Remove large/unwanted files from history | Optimize git (.git/objects cleanup) | Clean stale refs

--cfg flag:

  • Remove deprecated cfg settings | Clean unused env vars
  • Update outdated cfg formats | Validate cfg consistency | Remove duplicate entries

--all flag:

  • Comprehensive cleanup all areas | Generate detailed report
  • Suggest maintenance schedule | Provide perf impact analysis

--dry-run flag:

  • Show what would be cleaned w/o changes | Estimate space savings & perf impact | ID risks before cleanup

--watch flag:

  • Monitor & auto-clean new artifacts | Continuous cleanup during dev | Prevent temp file accumulation | Real-time maintenance

Integration & Best Practices

Research requirements:

  • Project patterns→C7 framework-specific cleanup | Build tools→verify safe procedures for stack
  • Git ops→WebSearch safe practices & warnings | Deps mgmt→check official package mgr guidance
  • Never cleanup w/o understanding impact - verify patterns | Cite sources: // Source: [cleanup guide ref]

Report Output:

  • Cleanup summaries: .claudedocs/reports/cleanup-<type>-<timestamp>.md
  • Space savings: .claudedocs/metrics/cleanup-savings-<timestamp>.md
  • Ensure dirs: mkdir -p .claudedocs/reports/ .claudedocs/metrics/
  • Include location: "📄 Cleanup report saved to: [path]"

Deliverables: Cleanup report w/ space saved, perf improvements, maintenance recommendations, safety analysis & cleanup strategy docs.