why-commentslisted

# Why Comments Flag comments that say *what* the code already says. Keep every comment that explains *why*. The user chooses which flagged comments to remove. ## Definition A comment is **redundant** if deleting it loses no information. Test: remove the comment mentally. Could a reader still understand the code from the code alone? If yes, the comment is redundant. A comment is **valuable** if it carries information the code cannot convey, such as a reason, a constraint, a history, or a warning. When unsure, keep it. ## Invocation | Command | Behavior | |---|---| | `/why-comments` | Find the 10 lowest-value comments. | | `/why-comments <number>` | Find that many lowest-value comments. | | `/why-comments all` | Find every low-value comment. | ## Workflow checklist Copy this checklist and track your progress: ``` Comment Prune Progress: - [ ] 1. Resolve the limit (default 10) - [ ] 2. Search source files for comment candidates - [ ] 3. Rank from most to least redundant - [ ] 4. Get each candidate's age with git blame - [ ] 5. Present the table and ask for approval - [ ] 6. Remove only approved comments - [ ] 7. Run lint and typecheck ``` ## 1. Search 1. Resolve the limit from the invocation. Default is 10. 2. Search source files. Skip generated output, vendored dependencies, lockfiles, and documentation. 3. Rank candidates from most redundant to least. 4. Get each candidate's age with `git blame` (see Comment age). If a subagent is available, delegate the read-