refactoring-analysis

To identify code smells and refactoring opportunities, analyze your codebase against Martin Fowler's catalog to detect duplicated code, long functions, and high coupling, producing a prioritized report with actionable recommendations.

Prepare for a refactoring sprint by running an architectural health audit to classify structural issue severity, generating a targeted report with prioritized findings and concrete before/after sketches saved to docs/_refacs/.

Refactoring analysis applies across common programming languages, detecting broad code smell categories like primitive obsession and complex conditionals to guide remediation regardless of the specific language used.

The best way to map detected code smells to refactoring techniques is by applying Fowler's catalog, which provides recommended refactoring methods complete with before/after sketches and rationale for each structural issue.

Refactoring analysis should not be used for style or formatting issues, performance optimization, or security audits, as it specifically targets structural code quality and architectural health improvements.

You can get a structured architectural health report by analyzing the codebase to detect coupling and large modules, which outputs a prioritized findings document with actionable recommendations saved directly under docs/_refacs/.