code-cleanup

Dead code removal is performed safely using a dual-pass discovery and verification workflow. This process identifies unused symbols and validates their usage with static analysis tools and git integration, ensuring high-confidence suggestions that maintain code integrity.

Automated Python refactoring is achieved through a categorized cleanup process that targets specific issues like dead code and latent bugs while strictly avoiding style-only changes or public API modifications. This ensures net-LOC neutral changes without scope creep.

Yes, verifying duplicated logic and latent bugs is handled by a mandatory verification pass that follows the initial discovery phase. This dual-pass system ensures accuracy by validating symbol usage and confirming code integrity before presenting any findings.

Python code cleanup requires git integration to validate symbol usage and ensure code integrity during the refactoring process. This integration helps maintain file size constraints while systematically sweeping the repository for technical debt.

A dual-pass discovery workflow ensures high-confidence refactoring suggestions by verifying potential cleanups before presenting them. Unlike single-pass static analysis, this method prevents regressions by validating symbol usage and ensuring every proposed change is net-LOC neutral.

Automated refactoring should not be used for style-only changes or public API modifications. It is specifically designed to target trivial refactoring wins like dead code, duplicated logic, and stale comments while maintaining strict file size constraints and avoiding scope creep.