refactor-clean

To safely remove dead code from a large repository, you need a workflow that identifies unused exports and dependencies, verifies tests pass before applying deletions, and provides a deterministic rollback if behavior breaks. This ensures correctness while cleaning up evolving codebases.

Dead code analysis with test verification identifies unused files, exports, and dependencies, then runs tests to confirm behavior remains correct before deletion. You need it when maintaining large codebases where risky deletions must be detected and reviewed before integration.

You can generate a dead code analysis report by running static analysis on a codebase to identify unused exports, files, and dependencies, verifying tests before deletions, and consolidating the findings into a consolidated dead-code-analysis.md report for review.

Dead code cleanup requires integration with existing test runners and static analysis tools to verify correctness before applying changes. It uses a deterministic rollback workflow to confirm tests pass, ensuring safe deletions within large repositories.

The best way to handle risky deletions during a refactor is to use a safe deletion workflow that verifies tests before removing unused dependencies, provides rollback capability, and generates a review report to ensure no behavior breaks before integration.

You should not use automated dead code removal without test verification when your repository lacks a deterministic test suite, as risky deletions of unused exports or dependencies require passing tests and rollback capability to confirm correctness before integration.