No Comments

by backnotprop3a604672c46cNo license1.3K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

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

Instructions onlySoftware Development
AI-generated overview

Removes unjustified code comments by spawning a review subagent, fixing accepted findings, and offering encodings for constraints.

What it does
This skill orchestrates a review pass over a caller's files or the current diff against a base branch. It spawns a Comment Sicko subagent (or a general subagent, or runs the prompt itself) to flag comments, then inspects the report and diff to reject invalid findings. It fixes accepted findings with the smallest root-cause change and offers to encode claimed constraints as type, runtime, test, or CI lint checks before deleting them. It finishes with a report of deletions, restorations, reruns, fixes, encoding offers, and open work.
When to use it
Use it when a codebase or diff contains comments that may be dead, misleading, or unjustified and you want them reviewed and removed. It fits a workflow where a separate reviewer subagent is available or where the prompt can be run directly. It is intended for interactive use, since constraint encodings require approval.
Requirements
Requires an agent harness with a subagent tool (Task, Agent, task, or spawn_agent) or the ability to run the referenced prompt directly. It reads references/comment-sicko.md and may invoke /how, /why, and /architect commands. It ships no scripts and needs no credentials or network access beyond the agent.

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. Spawn 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 [blocked] 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.
  2. Inspect its report and diff. 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 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.
  3. Fix trivial accepted flags directly by deleting a dead path, dropping a parameter, or using the real API. If any fix needs a shape, run /architect once for the accepted set and surrounding code. Stop at the sketch. Architect shapes. Step 4 implements.
  4. Implement the smallest root-cause fix in scope. Remove every named workaround. If the root cause is out of scope, land the smallest in-scope fix and report the rest open. The principle-fix-root-causes and principle-redesign-from-first-principles skills guide intent only. Neither authorizes widening the fence nor fixing instances outside it. Never bolt on symptom guards.
  5. Constraint comments say 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.
  6. Report the deletion count, restored comments, reruns, architect sketch, fixes, encoding offers, encodings, unenforced constraints, and other open work.

Source and attribution

Source:backnotprop/pstackinskills/no-commentsat commit3a60467

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal