code-cleanup

Automate dead code and unused imports removal by running a workflow that uses knip as the primary detector, applying safe fallbacks to ESLint or TypeScript tooling to identify and eliminate unnecessary files and declarations.

Yes, the cleanup workflow applies risk-based auto-removal for low and medium risk changes, while requiring explicit user confirmation for high-risk modifications and providing a rollback path to restore the previous state if needed.

Protect critical files by creating a .cleanup-ignore file, which the cleanup workflow respects during execution to prevent automatic removal of essential code, declarations, and unused imports across your refactored codebase.

Yes, if knip is not available, the workflow safely falls back to standard ESLint and TypeScript tooling to detect and remove unused imports and dead files during maintenance, pre-commit runs, or CI pipelines.

Verify post-cleanup stability by running the built-in post-cleanup verification steps, which validate the changes and ensure the codebase remains functional after dead code and unused imports are eliminated.

Run automated dead code detection during codebase maintenance, pre-commit runs, or CI pipelines to continuously eliminate drift and clutter caused by unused imports and dead files across your project.