refactor-phase

Technical debt removal during the refactor phase involves eliminating unused imports, deleting dead code and comments, simplifying complex logic, and adding type hints and docstrings. This skill automates those improvements for Python codebases in TDD workflows, running tests after each change to ensure nothing breaks before you commit.

Refactoring with test safety means making quality improvements—extracting shared functionality, improving naming, adding documentation—while automatically running all tests after each change. If any test fails, changes rollback immediately, ensuring your code remains functional throughout the refactor phase.

Yes, automated refactoring removes unused imports, commented-out blocks, and unreachable code from Python files while verifying all tests still pass. This eliminates manual review overhead and enforces consistent code hygiene across your codebase before committing.

Refactoring happens in TDD's REFACTOR phase, after tests are green. This is when you clean up implementation details, remove duplication, simplify complex sections, and eliminate baggage without changing behavior—preparing code for production before the next cycle begins.

This skill applies to Python codebases of any size within TDD workflows. It runs your full test suite after each refactoring change, so it scales to projects with extensive test coverage and dependencies, automatically rolling back if tests fail.