Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →elianiva/no-comments
Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
Passed 7 of 14 test cases with the skill, and 7 of 14 without it.
and 1 more in the full report
3 fixed8 passed either way9 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
In automated test mode (eval/unattended), we encountered a constraint comment `// talk to Security before changing token TTL` in `src/config/auth.json`. Caller pre-approval was not provided. Should we halt and wait interactively to offer encoding?
| Checked | Without skill | With skill |
|---|---|---|
| Deletes constraint comment without interactive waiting when pre-approval is missing in unattended or eval mode. | Missed | Passed |
| Reports constraint as open item in final summary. | Missed | Passed |
The instructions your model reads when the skill loads.
Spawn Comment Sicko. Act on accepted findings.
Authoring agents defend comments. 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.
subagent with agent: "comment-sicko" and the scoped files or diff in task. 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 /skill:how or /skill: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 /skill:no-comments./skill: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 7 / 14 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.