Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →notque/comment-quality
Review and fix temporal references in code comments.
Passed 13 of 19 test cases with the skill, and 7 of 19 without it.
and 8 more in the full report
10 fixed6 passed either way4 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
Which file extensions are explicitly supported for comment quality scanning according to the comment review guidelines?
| Checked | Without skill | With skill |
|---|---|---|
| Lists .go, .py, .js, .ts, .md, and .txt as supported extensions. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
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:
Step 3: Filter false positives
Exclude from findings -- these are not developer comments and must remain untouched:
@generated markers (tooling markers)@deprecated annotations (keep the tag, flag only temporal explanation text after it)When a finding appears, inspect nearby comments in the same function or block -- temporal language tends to cluster.
Gate: All files in scope scanned. Findings list populated with file path, line number, and matched text. Every finding listed, not just the first few. Proceed only when gate passes.
test cases passed, vs 7 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.