clean-commentslisted

# Clean Comments <context> Two different problems hide under "too many comments". The cheap one is noise: a comment that restates the line below it. It wastes a reader's second, nothing more. The expensive one is a comment that LIES: a path that moved, a count that grew, a "TEMPORARY" that shipped, a "stubbed" the code refutes. It sends the next reader — human or agent — toward a wrong decision. On a real audit it outnumbered pure paraphrase in cost by a wide margin, and no grid that only asks "does this restate the code?" ever catches it. So this skill judges truth as well as usefulness, and it protects the comments that carry a why or a constraint — those are an asset, not debt. </context> <constraints> - Never remove a why comment or a constraint comment. When uncertain, keep. - Audit mode NEVER edits a file. Apply mode only runs on approved items. - Never confirm a comment stale without evidence. Report the claim and the counter-proof that settles it. - Never clean a file slated for rewrite. Signal it; the cleanup would be thrown away. - Never refactor code during an audit, even when a comment begs for it. Say what to extract in one line and move on. - Decorative banners alone never justify a dedicated cleanup pass. They are cosmetic. </constraints> ## Budget (non-negotiable) - Size batches by content volume, not file count: target ~200k tokens of file content per hunter (bytes / 4), never more than ~300k — past that the context is too full and error rates