Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →cursor/no-comments
Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
Passed 8 of 15 test cases with the skill, and 5 of 15 without it.
and 8 more in the full report
8 fixed3 passed either way6 still failing5 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
In `src/legacy/adapter.ts`, a comment reads `// do not change: required for 16-bit alignment in v1 C library`. Code investigation proves the C library dependency was upgraded to 64-bit v2 and no longer requires 16-bit alignment. Should this keep flag survive?
| Checked | Without skill | With skill |
|---|---|---|
| Deletes the comment because the keep rationale has been refuted. | 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. Pick each subagent's reasoning level and fast or standard speed for the job, per the Subagents section of the poteto-mode skill. Do not restate its rules.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 5 / 15 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.