refactor-cleaner

Dead code in a monorepo is identified by locating unused exports, variables, and redundant dependencies, then safely removing them with validation and testing. Changes are documented in DELETION_LOG.md to maintain traceability and prevent regressions.

The safest way to clean up unused dependencies is through incremental removal with safety checks and validation. You document every change in DELETION_LOG.md and run tests to ensure no regressions occur during the refactoring process.

Consolidating duplicate code involves merging redundant implementations into a single reusable component. This refactoring is performed with incremental confirmations and validation steps to ensure the consolidated code maintains functionality.

Dead code removal works across multiple modules in a monorepo by identifying unused exports and dependencies spanning the entire project. It safely cleans and consolidates code across modules while logging deletions for traceability.

Refactoring legacy codebases requires careful validation and testing to avoid regressions. Limitations include the risk of breaking hidden dynamic imports, which necessitates incremental confirmations and audit logging during the cleanup process.