How does it handle dynamic references like reflection or getattr?

The skill specifically scans for dynamic patterns. If it cannot definitively prove code is dead due to potential dynamic usage, it classifies the code as 'Yellow' (Requires Manual Check) rather than deleting it.

Can I use this for simplifying complex logic?

No, this skill is focused strictly on cleanup and removal. For logic simplification or rewriting, you should use the 'code-simpler' skill instead.

Does it keep a record of what was deleted?

Yes, Phase 5 of the workflow requires documentation. It automatically generates a refactoring report in your docs folder documenting every change and its justification.

Is it safe to delete code automatically with this skill?

Yes. Refactor Cleaner uses a strict verification process including grep searches, dependency mapping, and mandatory test execution to ensure code is truly unused before deletion.

Refactor Cleaner

Name: Refactor Cleaner
Author: aimskr

byaimskr

0•

Herramientas para Desarrolladores

Identifies and safely removes dead code, unused imports, and redundant logic to streamline codebases and reduce technical debt.

Refactor Cleaner is a specialized utility designed to maintain codebase health by systematically purging unreachable or obsolete code. Unlike simple linters, it employs a rigorous five-phase workflow that includes deep architectural exploration via code-explorer, multi-method verification to catch dynamic references, and mandatory test validation. It is particularly effective for large-scale cleanup operations where manual identification of unused functions or imports is error-prone, ensuring that every deletion is documented and safe for production environments.

Características Principales

010 GitHub stars

02Safety-first checks for dynamic references and API endpoints

03Deep dependency mapping via code-explorer integration

04Integrated testing and rollback mechanisms for failed builds

05Multi-phase verification workflow (Scan, Verify, Classify, Clean, Document)

06Automated refactoring documentation and audit trails

Casos de Uso

01Cleaning up legacy projects by removing accumulated technical debt and dead features

02Optimizing build times and bundle sizes by purging unused imports and modules

03Preparing codebases for major migrations by identifying and removing deprecated logic

Características Principales

010 GitHub stars

02Safety-first checks for dynamic references and API endpoints

03Deep dependency mapping via code-explorer integration

04Integrated testing and rollback mechanisms for failed builds

05Multi-phase verification workflow (Scan, Verify, Classify, Clean, Document)

06Automated refactoring documentation and audit trails

Casos de Uso

01Cleaning up legacy projects by removing accumulated technical debt and dead features

02Optimizing build times and bundle sizes by purging unused imports and modules

03Preparing codebases for major migrations by identifying and removing deprecated logic