simplify-codebase

To identify and remove dead code after refactoring, this Skill analyzes git history and dependency graphs to classify files as fresh, stale, or dead, then archives unused files to a separate directory while preserving provenance.

The best way to clean up stale code in a repository is to orchestrate a multi-agent process that detects project type, resolves test commands, and simplifies active code according to project standards for improved maintainability.

Yes, you can resume codebase cleanup across multiple sessions because the Skill includes built-in resume functionality, allowing you to continue the archiving and simplification tasks without restarting the entire analysis from scratch.

The codebase cleanup process preserves history for archived files by moving dead files to an archive directory with provenance, ensuring that the original context and git history remain intact for future reference.

Code simplification handles different project types by automatically detecting the project type and resolving the appropriate test commands, then cleaning up active code for better readability and consistency according to established project standards.

You should avoid automating codebase cleanup if your repository lacks sufficient git history or dependency graphs for staleness analysis, as the Skill relies on these inputs to accurately classify files and safely archive unused code.