dead-code-eliminator

To find and remove dead code, this Skill uses static analysis, code coverage data, and grep to identify unreachable branches, uncalled functions, and dead feature flags. It then guides you through a verification and deprecation workflow to ensure safe removal.

The safest way to clean up unused functions and dead feature flags is using a structured workflow that verifies candidates before deletion. This approach prevents accidental removal of essential code by guiding you through deprecation and verification steps.

Yes, code coverage data is required alongside static analysis and grep to accurately identify unreachable code branches. This combination ensures comprehensive detection of dead code candidates within your software project.

Yes, you can reduce technical debt by removing uncalled public functions. The Skill detects public functions with no apparent callers and facilitates their safe deletion, improving overall codebase maintainability and reducing complexity.

The best way to clean up old code paths after a feature migration is to identify now-unused functions and associated tests for safe removal. This reduces codebase size, lowers technical debt, and improves build times.

You should avoid deleting dead code candidates immediately if they might be called dynamically or through reflection. The Skill uses a verification and deprecation process precisely to prevent accidental removal of essential code during static analysis.