no-comments

Reviews code diffs with a Comment Sicko subagent and removes or encodes unjustified comments.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/jeremybrasher/grokbot-skills --skill no-comments-jeremybrasher
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: no-comments
Source: https://github.com/jeremybrasher/grokbot-skills/tree/main/collections/pstack/skills/no-comments
Command: npx skills add https://github.com/jeremybrasher/grokbot-skills --skill no-comments-jeremybrasher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases accumulate stale, misleading, or redundant comments that clutter diffs and mislead maintainers. This Skill audits comments in a diff, deletes unjustified ones, fixes the underlying code issues they hide, and converts real constraints into enforceable checks. ## Core Features & Use Cases - Subagent-driven comment audit: Spawns a Comment Sicko subagent against the current diff or caller-provided files, then validates its report before acting on any finding. - Root-cause fixes over comment patches: Implements the smallest in-scope fix for accepted findings instead of bolting on symptom guards, optionally running an architect pass for shape decisions. - Constraint encoding: Converts "do not remove" or "talk to X" comments into type, runtime, test, or CI lint enforcement after explicit approval. - Use Case: Before merging a pull request, run this Skill against the diff to strip dead comments, fix the issues they documented, and turn genuine constraints into CI checks. ## Quick Start Run the no-comments skill on my current diff against main to audit and clean up code comments.

Frequently Asked Questions about no-comments

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I remove unnecessary comments from a code diff?▼

Run this Skill against your current diff or supplied files. It spawns a Comment Sicko subagent to flag unjustified comments, validates each finding, deletes dead comments, and fixes the underlying code issues they concealed.

How to enforce code constraints without comments?▼

Constraint comments like "do not remove" are converted into enforceable mechanisms such as type checks, runtime assertions, tests, or CI lint rules. Encoding requires explicit interactive approval or caller pre-approval in unattended runs.

Does this delete all comments in my code automatically?▼

No. It only acts on accepted findings after validating the subagent report, rejecting scope escapes and misstated deletions. Comments about code that cannot be changed are kept, and ambiguous kills are not restored or removed without proof.

What happens when required inputs are missing?▼

The Skill returns a HOLD instead of guessing. It names the missing object, input, or write authority and stops, since a HOLD is treated as a valid return value rather than a delay before proceeding.

When should I not use automated comment cleanup?▼

Avoid it when the description trigger is not met, required inputs are unavailable, or a narrower skill fits better. It also refuses drive-by refactors and fixes outside the defined diff scope.