refactor

Code analysis for refactoring identifies structural weaknesses across files, detecting code smells like duplicated logic, god functions, and scattered concerns to produce a prioritized improvement plan.

The best way to prioritize code quality improvements is to consolidate cross-file pattern findings from multiple agents into a ranked, actionable refactoring plan that targets the most impactful structural changes first.

Yes, you can analyze specific file paths and globs for code smells using various scope resolutions, including targeted directory sampling or full project analysis, to detect structural issues like god functions and duplicated logic.

You generate a prioritized refactoring plan by running structural analysis on the complex module, which evaluates cross-file patterns and ranks actionable recommendations to reduce complexity and save manual analysis time.

Yes, deep code analysis detects duplicated logic and god functions by evaluating structural improvement opportunities across the codebase, identifying specific code smells that degrade maintainability and increase complexity.

Use quick mode for rapid identification of impactful structural improvement areas in specific directories, and use deep analysis for comprehensive cross-file pattern evaluation and consolidated findings across the entire project.