comment-quality

# Comment Quality Skill Review code comments for temporal references, development-activity language, and relative comparisons. Produces structured reports with actionable rewrites that explain WHAT the code does and WHY, only WHAT the code does and WHY. Supports `.go`, `.py`, `.js`, `.ts`, `.md`, and `.txt` files. ## Instructions ### Phase 1: SCAN **Goal**: Identify all comments containing temporal, activity, or relative language. **Step 1: Determine scope** Read the repository CLAUDE.md first to pick up any project-specific comment conventions. Scan only what was requested. If user specifies files, scan those files. If user specifies a directory, scan that directory. Honor the explicit scope -- even if you suspect other files have issues, honor the explicit scope and suggest expansion separately at the end. If user explicitly requests auto-fix, enable it. Otherwise present findings for review. For large codebases, group findings by directory when reporting. **Step 2: Search for temporal patterns** Flag every instance of the following categories. No temporal word is "harmless" -- all temporal language ages poorly and must be rewritten regardless of how innocuous it seems: - **Temporal words**: "new", "old", "previous", "current", "now", "recently", "latest", "modern" - **Development activity**: "added", "removed", "deleted", "updated", "changed", "modified", "fixed", "improved", "enhanced", "refactored", "optimized" - **State transitions**: "replaced", "migrated", ...