refine

To polish uncommitted changes, run a code-cleanup pass on your Git working tree to simplify logic and improve comments. This process identifies edited files, applies standard refactoring patterns, verifies syntax, and generates per-file diffs for review.

Comment improvement preserves docstrings, JSDoc, GoDoc, and RustDoc by default. It only removes them if vacuous or restating the signature with zero info, updates inaccurate notes instead of deleting them, and prunes dead TODOs while preserving why explanations.

Yes, you can refactor code across multiple edited files in a single pass. The tool reads all identified edited files in parallel, applies simplifications, and ensures all modifications stay strictly within the uncommitted scope of your Git working tree.

The best way to clean up obvious comments and dead TODOs is to run a targeted code-cleanup on uncommitted changes. This removes obvious statements, prunes outdated notes, preserves why explanations, and updates vacuous documentation to ensure accurate commentary.

This code cleanup tool only modifies files with uncommitted changes in your Git working tree. It explicitly identifies edited files and ensures all simplifications and comment improvements stay within the uncommitted scope, leaving committed history untouched.