no-comments

Removes unjustified code comments by auditing a diff with a review subagent and fixing root causes.

6.6k|542|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/cursor/plugins --skill no-comments
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: no-comments
Source: https://github.com/cursor/plugins/tree/main/pstack/skills/no-comments
Command: npx skills add https://github.com/cursor/plugins --skill no-comments

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codebases accumulate stale, misleading, or noise comments that obscure intent, and removing them safely requires judging which comments encode real constraints. This Skill audits a diff for unjustified comments, deletes the dead ones, and encodes legitimate constraints into types, tests, or lint rules.

Core Features & Use Cases

  • Subagent-driven audit: Spawns a Comment Sicko subagent to flag comments in the current diff, then validates each finding against scope rules and exception protections.
  • Root-cause fixes: Implements the smallest fix behind each accepted flag, optionally running an architect pass for structural changes.
  • Constraint encoding: Converts "do not remove" style comments into enforceable type, runtime, test, or CI lint checks after approval.
  • Use Case: Before merging a pull request, run the audit to strip redundant comments from the diff, restore any wrongly deleted exception-protected notes, and replace a "talk to X before changing" comment with a CI lint rule.

Quick Start

Run the no-comments skill on my current diff against main to remove unjustified comments and fix the underlying issues.

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 the audit on your current diff against the base branch. A review subagent flags unjustified comments, each finding is verified against scope and exception rules, and accepted flags are fixed by deleting dead code or using the real API.

How to handle comments that say do not remove or do not change?

Constraint comments are kept only when they cover something that cannot be changed. Otherwise the cheapest in-scope encoding is offered as a type, runtime check, test, or CI lint rule, and the comment is deleted after approval.

Can this delete comments that document real constraints?

Comments protected by exact exceptions with scoped proof are restored, and keeps survive when they document things outside the code's control. Ambiguous kills are not restored, but refuted or ambiguous keeps are deleted.

What happens when a comment flags a problem outside the diff scope?

The smallest in-scope fix is landed and the remaining out-of-scope work is reported as open. The audit never widens the fence to fix instances beyond the caller's files or diff.

What are the limitations of automated comment removal?

Encoding constraints into types or lint rules requires interactive approval, or pre-approval in unattended runs. A second rejected subagent report is left open and the run fails rather than guessing.