refactor-clean

To safely remove dead code, use static analysis tools like knip, depcheck, and ts-prune to identify unused exports and files, then execute deletions only after verifying that your full test suite passes.

The safest workflow for pruning unused code generates a consolidated report categorized by severity, enforces a full test run before applying any deletions, and supports rollback if the test suite fails.

Static analysis identifies dead code by scanning the project with tools like knip and ts-prune to surface unused dependencies, files, and exports, consolidating the results into a structured report with SAFE, CAUTION, and DANGER categories.

Yes, rollback is supported if tests fail. The deletion workflow enforces running the full test suite before applying changes and automatically initiates a rollback if any test failures are detected.

Yes, a full test suite is required. The workflow enforces running tests before applying any deletions to ensure that removing unused files, dependencies, and exports does not introduce hidden risks or break functionality.

You should avoid automated dead code cleanup when your project lacks a comprehensive test suite, as the deletion workflow relies on passing tests to verify safety and trigger rollback if failures occur.