suggest

Automated code refactoring is applied safely by enforcing criteria: changes must be low effort, behavior-preserving, reversible, and provide measurable benefit. Proposals meeting these thresholds are auto-implemented, while complex modifications prompt for human review.

Improving code maintainability automatically involves analyzing the codebase to generate context-aware proposals. It targets readability by renaming unclear variables, extracting duplicated logic into functions, adding docstrings, and removing dead code.

A guided decision flow classifies improvement suggestions into auto-implementable or human-review categories. It evaluates safety criteria like low risk and reversibility, applying safe changes directly and prompting for human input on complex refactoring decisions.

Yes, you can automatically remove dead code and extract duplicated logic from modules. The skill analyzes the codebase to identify these maintainability issues and auto-applies the fixes when the changes are deemed low-risk and reversible.

You should avoid automated refactoring when changes require high effort, alter behavior, or lack reversibility. Proposals failing the safety criteria are not auto-applied, ensuring risky modifications are deferred for manual human decision-making.

No, the automated improvement tool requires no specific dependencies or frameworks. It operates across typical software projects by analyzing the codebase directly to generate and apply safe, maintainability-focused proposals.