refactoring-analysis

Code smell detection scans specified directories for bloated functions, duplicated code, and high coupling. This process identifies structural issues based on Martin Fowler’s catalog, turning vague technical debt concerns into a clear, prioritized refactoring report.

You can analyze technical debt across flexible scopes, targeting an entire repository, a specific module, or a feature area. This generates a prioritized refactoring report saved to the docs folder, isolating structural issues for immediate team consumption.

Prioritizing refactoring tasks for domain-driven designs involves applying optional SOLID analysis alongside standard code smell detection. This evaluates structural issues and coupling to produce a prioritized report tailored to your domain logic.

Code smell detection works across any language or paradigm. It scans your specified directory to locate duplicated logic, high coupling, and structural issues, ensuring comprehensive smell detection regardless of your tech stack.

You generate a refactoring report by analyzing your source folder for structural issues. The report is saved automatically to the docs/_refacs folder, providing an actionable refactoring plan for immediate team consumption.

Automated refactoring analysis may not be suitable for highly dynamic or runtime-dependent logic where structural issues are not easily detectable through static directory scanning. It focuses on code smells, duplicated code, and coupling.