cleanup

To automatically remove unused imports and dead code, run a project-wide cleanup scan that applies safe auto-fixes to source and test files while surfacing dead code and duplicate logic for user confirmation before edits are applied.

The best way to auto-fix code quality issues before a release is to run an automated cleanup that removes trivial issues like whitespace and unused imports, runs the test suite, and reverts problematic changes if tests fail to prevent regressions.

Yes, you can automatically clean up trailing whitespace, inconsistent blank lines, and large commented-out code blocks when safe, using an automated cleanup tool that operates on project source and test files to apply low-risk fixes.

Yes, automated code cleanup can optionally run configured project formatters and the test suite to verify changes, automatically reverting any problematic edits if tests fail to ensure no functional regressions are introduced.

Risky refactoring changes like removing dead code, duplicate logic, and mismatched tests are detected and presented for human-in-the-loop user confirmation before they are applied, ensuring safe code hygiene improvements.

A limitation of automated code cleanup is that it only auto-fixes trivial issues like unused imports and whitespace, requiring user approval for riskier edits involving dead code and duplicate logic, and reverting changes if tests fail.