clean-code-reviewer

To identify code duplication and redundancy, analyze module boundaries and naming conventions to consolidate duplicate logic into shared utilities and extract reusable modules, producing a prioritized refactor plan.

Planning refactoring for maintainability involves analyzing module boundaries and test coverage to produce actionable, prioritized refactor recommendations with evidence-based rationale and non-destructive suggestions.

To generate unit and integration tests after refactoring, suggest testing enhancements that guard against regressions, ensuring the consolidated shared utilities and extracted modules maintain functional integrity.

Yes, this code review approach works without existing test coverage by analyzing current module boundaries and producing a suggested test plan alongside a prioritized refactor plan to establish future regression guards.

Duplicate utilities across modules occur when similar logic is implemented separately; consolidating these into shared utilities and extracting common patterns into reusable modules resolves the redundancy.

You should not use automated refactoring suggestions when immediate non-destructive execution is required without review, as this approach outputs a prioritized plan with evidence-based rationale requiring validation before implementation.