Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →backnotprop/no-comments
Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
Passed 13 of 18 test cases with the skill, and 6 of 18 without it.
and 11 more in the full report
10 fixed7 passed either way5 still failing1 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.
A developer executes a comment cleanup command from the project root without providing any file paths, commit range, or explicit scope parameters. What exact file scope must be analyzed?
| Checked | Without skill | With skill |
|---|---|---|
| Defaults the evaluation scope to the git diff against main including the working tree. | Missed | Passed |
The instructions your model reads when the skill loads.
Spawn Comment Sicko. Act on accepted findings.
Defer to Comment Sicko's fresh perspective.
Use the caller's files or diff. Otherwise use the current diff against the base branch, default main, including the working tree.
Task with subagent_type: "comment-sicko". Pass the scope. Do not restate its rules. If your harness doesn't have comment-sicko registered as a subagent (any harness other than Cursor with the pstack plugin), spawn a general subagent instead: Agent in Claude Code (subagent_type: general-purpose), task in OpenCode (subagent_type: general), spawn_agent in Codex. Its prompt is references/comment-sicko.md verbatim, then the scope. If your harness has no subagent tool, as in Pi without an extension, run that prompt yourself in a fresh pass over the scope.MUST KILL reasons, and flags that treat kept intentional code as guilty. Reshape flags on our-code surprises stay actionable. Do not restore those comments. A keep survives only with proof it is about something we cannot change. Audit missed scoped lint and TypeScript suppressions. Correctness or safety suppressions stay actionable MUST KILLs. Restore deletions only with exact exceptions and scoped proof. Before accepting thin IMPORTANT or do not remove kills or keeps, run /how or /why on their symbol. If a kill is ambiguous, do not restore. If a keep is refuted or still ambiguous, delete it. Revert and rerun one rejected report with the failure named. Reject a second, report it open, and fail /no-comments./architect once for the accepted set and surrounding code. Stop at the sketch. Architect shapes. Step 4 implements.do not remove, do not change wording, or talk to X before changing. Leave keeps about things we cannot change. Offer the cheapest in-scope type, runtime, test, or CI lint. Wait for interactive approval. Unattended and eval require caller pre-approval. If approved, encode then delete. Otherwise delete, report the constraint open, and sketch out-of-scope work.test cases passed, vs 6 / 18 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.