comment-cleanup

Remove unnecessary comments by identifying outdated, redundant, or overly verbose remarks that don't add clarity. Keep only comments that explain *why* code exists, not *what* it does or how it changed—place them above the relevant code block, never at the end of lines.

Best practices for code comments include placing them above the code they describe, keeping them minimal and focused on intent rather than process, removing commented-out code entirely, and avoiding end-of-line comments that disrupt readability.

Clean up commented-out code by deleting it entirely rather than leaving it as comments. Version control systems track old code, making commented blocks unnecessary clutter that obscures current logic and maintenance intent.

End-of-line comments reduce readability by splitting your visual focus between code and explanation. Placing comments above code creates clear separation, improves line length consistency, and makes logic flow easier to follow.

Yes, comment-cleanup guides automated refactoring of comments that violate best practices—removing process-oriented remarks, eliminating end-of-line comments, and deleting commented-out code across source files during maintenance tasks.