dead-code-cleanup

You can eliminate dead code across a TypeScript and Rust Tauri project by running frontend analysis with knip and backend analysis with Rust tooling. It identifies unused exports, files, dependencies, and dead code paths for cleanup.

The best way to detect unused exports and dependencies in a React frontend is using knip. It scans your TypeScript project to find unreferenced files and symbols, reducing maintenance burden during refactoring sprints.

Yes, you can scan a Rust Tauri backend for unused commands and dead code paths using Rust tooling. The skill enforces verifying these findings before deletion to ensure safe removal during release preparation.

To safely clean up unused code, you must verify all findings before deletion, prune the unused code, and iteratively re-run the analysis. Continue this workflow until the scan reports no dead code remains.

Yes, knip is required for frontend dead code detection. You run bunx knip to scan for dead code, verify the findings, and iteratively apply fixes until the scan reports no dead code is left.

You should run a dead code cleanup sprint during refactoring, cleanup sprints, and before releases. This reduces the maintenance burden and surface area of unreferenced symbols across your TypeScript and Rust codebase.