Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →michael-denyer/no-comments
Spawn the comment-sicko subagent, fix accepted findings, and offer encodings for claimed constraints.
Passed 17 of 20 test cases with the skill, and 12 of 20 without it.
and 4 more in the full report
6 fixed11 passed either way2 still failing1 broke4 errored
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
The comment audit subagent was rerun once for `lib/db.ts` after its first report was rejected for application code edits. The second report still contains application code edits. What should be done now?
| Checked | Without skill | With skill |
|---|---|---|
| Reports the issue open without running a third subagent iteration. | Missed | Passed |
| Fails the cleanup execution. | Passed | Passed |
The instructions your model reads when the skill loads.
On Codex, read the platform mapping, including its per-skill notes, before following this skill.
On GitHub Copilot, read the platform mapping, including its per-skill notes, before following this skill.
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.
Agent with subagent_type: "pstack:comment-sicko". Pass the scope. 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 12 / 20 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.