Menu

Individual skill

no-comments

0upvotes

Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.

skills/no-comments/SKILL.md

Read pinned source

Source commit 09909ebb5c0125e27fad3e57d96b81e832696d69

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
161
Repository last updated
Oct 5, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# No comments

Spawn Comment Sicko. Act on accepted findings.

Defer to Comment Sicko's fresh perspective.

## Scope

Use the caller's files or diff. Otherwise use the current diff against the base branch, default `main`, including the working tree.

## Steps

1. Call `delegate_task` with `mode: "async"` and the `judgment and prose` model from `orchestrator_capabilities`. Its brief is the text of `agents/comment-sicko.md` plus the scope: file paths, or the diff itself. Do not restate its rules. The child sees only the brief, and it is read-only. Drain it with `task_status`.
2. Inspect its report. It writes nothing, so you delete the comments it names. Reject application-code edits, scope escapes, exception-protected deletions, misstated `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 KILL`s. 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. Rerun one rejected report with the failure named in a fresh `delegate_task`. Reject a second, report it open, and fail `/no-comments`.