fec-refactor-clean

Safely removing dead code and unused dependencies requires baseline lint, type-check, test, and build validations. This Skill leverages knip, depcheck, and ts-prune to auto-clean safe items while flagging caution and danger items for review.

Cleaning up unused exports and deprecated routes without changing behavior requires a safe strategy based on existing lint, type-check, test, and build baselines. This Skill produces a structured cleanup plan that auto-cleans safe items and flags dangerous ones for manual review.

Yes, baseline lint, type-check, test, and build validations are required before running a frontend refactor cleanup. These validations serve as the safety net to ensure that removing dead code, unused exports, and unused dependencies does not change application behavior.

The dead code cleanup workflow handles risky unused dependencies by categorizing findings into SAFE, CAUTION, and DANGER levels. It auto-cleans SAFE items while flagging CAUTION and DANGER items for manual review in a structured markdown report.

Yes, you can use knip and ts-prune for incremental structural refactoring in large frontend repositories. This Skill applies a controlled cleanup strategy to identify and remove dead code and unused dependencies, reducing technical debt gradually.

When pruning deprecated routes and dead code, the limitation is that not all items are auto-removed. CAUTION and DANGER items require manual review to prevent behavior changes, meaning you must inspect the generated cleanup report before finalizing risky deletions.