dead-code-cleaner

To remove unused code and stale feature flags, this skill scans your repository using static analysis tools like eslint and pylint to identify dead variables and flags, then creates a pull request with the suggested safe removals.

Yes, dead code cleanup supports both Python and JavaScript repositories by running static analysis tools like pylint and eslint to detect unreferenced functions, unused imports, and dead variables across your codebase.

To safely clean up technical debt without breaking tests, this skill verifies all identified dead code removals against your existing test suites before generating a pull request summarizing the code size reduction.

The best way to scan your repository for unreferenced functions and imports is to run a static analysis skill that groups identified dead code by file and opens a pull request with the suggested removals.

Yes, you can automate stale feature flag removal by regularly running this skill on your main development branch to detect hardcoded flags that are no longer active and keep the codebase lean.

A limitation of using static analysis for dead code detection is that it identifies unused functions, imports, and variables based on references, meaning dynamic code execution paths may require manual verification before removal.