skills.rest
jnyross
jnyrossCOMMUNITY
Explore all skills by this author →
GitHub

no-comments

Reviews code comments via a subagent and removes or encodes unjustified ones.

Updated Sep 2, 2026
Search Tags:#code quality#diff analysis#code review#refactoring#comments#subagent#lint
One-click install
npx skills add https://github.com/jnyross/pstack-muse --skill no-comments-jnyross
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: no-comments
Source: https://github.com/jnyross/pstack-muse/tree/main/skills/no-comments
Command: npx skills add https://github.com/jnyross/pstack-muse --skill no-comments-jnyross

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases accumulate stale, misleading, or unjustified comments that clutter code and misstate intent. This Skill audits comments in a diff or file set, deletes dead ones, and converts claimed constraints into enforceable types, tests, or lint rules. ## Core Features & Use Cases - Subagent-driven audit: Spawns a Comment Sicko subagent to review comments in the current diff against the base branch, then validates its report before acting. - Root-cause fixes: Implements the smallest fix behind each accepted finding, optionally running an architecture sketch step for structural changes. - Constraint encoding: Converts "do not remove" or "talk to X before changing" comments into type, runtime, test, or CI lint enforcement after approval. - Use Case: Before merging a pull request, run the audit to strip obsolete workaround comments and turn a "do not change wording" note into a CI lint rule. ## Quick Start Run the no-comments skill on my current diff against main to audit and clean up the 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 my code diff?▼

Run the skill against your current diff or specified files. It spawns a review subagent to flag dead or misleading comments, validates each finding, then deletes accepted flags and fixes the underlying root cause where needed.

How to enforce code constraints without comments?▼

Constraint comments like "do not remove" can be encoded as type definitions, runtime checks, tests, or CI lint rules. The skill offers the cheapest in-scope encoding, waits for approval, then deletes the comment once the constraint is enforced.

Does the comment audit work on files outside my current diff?▼

By default it scopes to the current diff against the base branch (default main) including the working tree. You can pass explicit files or a diff, and fixes outside that scope are reported as open work rather than applied.

What happens when a comment review finding is wrong?▼

Rejected findings are filtered before any edit: application-code edits, scope escapes, and misstated kill reasons are discarded. One rejected report is rerun with the failure named; a second rejection fails the run and reports it open.

When should I not delete a code comment?▼

Keep a comment only with proof it documents something the code cannot change, such as an external system behavior. Ambiguous keeps are deleted, while correctness or safety suppressions remain actionable findings rather than being restored.

Related Skills

Explore More Software Engineering Skills→
ferrarifankid04ferrarifankid04

review-security

Launches a security-review subagent to audit code changes in a repository diff.

Community
Intermediate
RamblurrRamblurr

Finishing a Development Branch

Verifies tests, formatting, and linting before creating a Pull Request.

Community
Intermediate
atelier-fashionatelier-fashion
159

reflect

Audit recent code changes for correctness, conventions, architecture, and testing.

Official
Advanced
cursorcursor
6.6k

no-comments

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

Official
Advanced