code-refactor

Safely refactor large modules by applying a phased workflow: identify code smells, execute Phase A quick wins, Phase B structural improvements, and Phase C architectural changes, while validating tests and maintaining rollback steps.

Code smells are indicators of deeper issues in your codebase. You identify refactoring opportunities by analyzing JavaScript, TypeScript, or Python projects to document long methods and deep class hierarchies that require structural improvements.

Apply Martin Fowler's methodology through a phased refactoring workflow: start with Phase A quick wins, progress to Phase B structural improvements, and finish with Phase C architectural changes, ensuring validated tests and clear rollback steps.

Yes, this refactoring workflow explicitly supports TypeScript projects, along with JavaScript and Python, to identify and refactor long methods and deep class hierarchies using structured phases and test validation.

The best way to plan an end-to-end refactoring workflow is to use automated artifact templates for execution and validation, integrate checks for maintainability, and follow clear rollback strategies to preserve behavior.

You should reconsider a phased refactoring approach if your project lacks validated tests, as the workflow relies on test guidance and clear rollback steps to safely execute structural and architectural changes without breaking behavior.