skills.rest
edivad1999
edivad1999COMMUNITY
Explore all skills by this author →
GitHub

no-comments

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

1|Updated Aug 26, 2026
Search Tags:#code review#refactoring#comments#subagent#kotlin#lint#code cleanup
One-click install
npx skills add https://github.com/edivad1999/stuc-stack --skill no-comments-edivad1999
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: no-comments
Source: https://github.com/edivad1999/stuc-stack/tree/main/skills/no-comments
Command: npx skills add https://github.com/edivad1999/stuc-stack --skill no-comments-edivad1999

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases accumulate stale, misleading, or unjustified comments that clutter code and drift out of sync with behavior. This Skill audits comments in a diff or file set, deletes the ones that add no value, and converts claimed constraints into enforceable checks. ## Core Features & Use Cases - Subagent-driven audit: Spawns a Comment Sicko subagent to review the current diff against the base branch, then validates its report before acting on findings. - Root-cause fixes: Implements the smallest fix for accepted findings, optionally running an architect pass when a fix needs a design shape. - Constraint encoding: Turns "do not remove" style comments into types, runtime checks, tests, or CI lints after interactive approval. - Use Case: Before merging a pull request, run the audit to strip dead comments, fix the underlying code issues they were papering over, and encode real constraints as tests. ## Quick Start Run the no-comments skill on my current diff against main to review 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 a code diff?▼

Run the no-comments skill on your current diff against the base branch, defaulting to main. It spawns a review subagent, validates each finding, deletes dead comments, and fixes the underlying code issues they described.

How to enforce code constraints instead of relying on comments?▼

Constraint comments like "do not remove" are converted into the cheapest enforceable mechanism: a type, runtime check, test, or CI lint. Encoding requires interactive approval, or caller pre-approval in unattended and eval runs.

Does the comment review work on Kotlin code?▼

Yes, the audit covers Kotlin code including @Suppress annotations and lint suppressions. Correctness or safety suppressions remain actionable findings, and scoped lint suppressions are checked for missed cases.

What happens when a comment review finding is wrong?▼

Rejected findings such as application-code edits, scope escapes, or misstated deletion reasons are filtered before any change. A rejected report is rerun once with the failure named; a second rejection is reported open and the run fails.

When should comments be kept instead of deleted?▼

A comment survives only with proof it documents something the team cannot change, such as an external constraint. Ambiguous keeps are deleted, and thin IMPORTANT or do-not-remove claims are verified against the symbol first.

Related Skills

Explore More Software Engineering Skills→
MartinoPoloMartinoPolo
1

mp-review

Review code diffs for correctness, security, and spec alignment.

Community
Advanced
THRISHAL12345THRISHAL12345

fix-ci

Analyze CI failure metadata and apply minimal code fixes.

Community
Intermediate
Srajangpt1Srajangpt1

dev5-review

Review TypeScript or JavaScript code for quality, correctness, and style.

Community
Intermediate
telihateliha

Lint Fix Expert

Fix the highest-priority lint warning one at a time with verification and a focused commit.

Official
Advanced