refactoring-analysis

To find refactoring opportunities in a legacy codebase, analyze the targeted modules to identify structural code smells, coupling issues, and DRY violations. This process detects bloaters and couplers, mapping each finding to recommended Fowler refactorings with precise file-line references.

Common code smells detected during a maintainability audit include bloaters, dispensables, couplers, conditional complexity, and DRY violations. Identifying these structural issues helps reduce complexity and lower change risk when planning safer architectural improvements.

Generate a prioritized refactoring report by analyzing your project for code smells and outputting the findings to docs/_refacs/. The report includes exact file-line references, coupling assessments, and before/after sketches mapping to Fowler-style techniques for actionable guidance.

Yes, you can analyze specific modules instead of an entire project for code smells. The analysis applies to targeted modules, individual features, or the whole codebase, making it flexible for localized code quality audits and module health reviews.

The best way to plan a refactoring sprint for legacy code is to run an architectural health review that identifies structural code smells and coupling issues. This produces a prioritized findings report with recommended Fowler refactorings to guide safer improvements.

Refactoring analysis provides specific guidance on fixing code smells by mapping each finding to Fowler-style techniques. It includes before/after sketches and DRY assessments to help teams understand the exact structural changes needed to reduce complexity.