skills.rest
lucasheriques
lucasheriquesCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

no-comments

Removes comments added by a code change using an adversarial review subagent.

Updated Sep 23, 2026
Search Tags:#code review#pull request#subagent#comment removal#lint suppression#diff audit#root cause fix
One-click install
npx skills add https://github.com/lucasheriques/pstack --skill no-comments-lucasheriques
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: no-comments
Source: https://github.com/lucasheriques/pstack/tree/main/skills/no-comments
Command: npx skills add https://github.com/lucasheriques/pstack --skill no-comments-lucasheriques

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often accumulate unnecessary or misleading comments that clutter diffs before review. This Skill audits only the comments a change added, deletes unjustified ones, and fixes the root causes that prompted them. ## Core Features & Use Cases - Scoped Comment Audit: Spawns a Comment Sicko subagent to hunt only comments introduced by the current diff against the base branch, leaving pre-existing comments untouched. - Root-Cause Fixes: Implements the smallest in-scope fix for accepted findings, optionally running the architect skill when a fix needs a shape decision. - Constraint Encoding: Converts "do not remove" style constraint comments into type, runtime, test, or CI lint enforcement after interactive approval. - Use Case: Before opening a pull request, run this Skill to strip the explanatory comments your change added, restore any wrongly deleted historical comments, and land fixes for dead code paths the comments were papering over. ## Quick Start Run the no-comments skill on my current diff to remove the comments this change added before review.

Frequently Asked Questions about no-comments

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

FAQPage Schema
How do I remove comments added by my code change before a PR review?▼

Run the no-comments skill on your current diff against the base branch. It spawns a Comment Sicko subagent to flag comments your change added, deletes accepted findings, and reports the deletion count and any open work.

Does the no-comments skill delete pre-existing comments in touched files?▼

No, only comments the current change added are in scope. A comment that existed before the change stays even in a touched file, and any deleted comment predating the change is always restored.

What happens to comments saying do not remove or do not change?▼

Constraint comments are kept if they concern things the code cannot change. Otherwise the skill offers the cheapest in-scope encoding as a type, runtime check, test, or CI lint, and deletes the comment only after interactive approval.

When should I not use automated comment removal on a diff?▼

Avoid it when the root cause behind a comment lies outside the change scope, since the skill only lands the smallest in-scope fix and reports the rest open. Correctness or safety suppressions also remain actionable rather than auto-deleted.

How does the skill verify ambiguous comment deletions?▼

Before accepting thin IMPORTANT or do-not-remove kills or keeps, it runs the how or why skill on the referenced symbol. Ambiguous kills are not restored, while refuted or still-ambiguous keeps are deleted.

Related Skills

Explore More Software Engineering Skills→
johnendjohnend
23

review-local

Identify defects and risks in local code changes with severity-ordered findings.

Community
Intermediate
CagesThrottleUsCagesThrottleUs

closing-review-loops

Batches code review fixes into one verified push before re-triggering external reviewers.

Community
Intermediate
mmdmcymmdmcy

teach

Explains code and subsystems by combining how and why skill investigations into plain-language teaching.

Community
Intermediate
jeremybrasherjeremybrasher

no-comments

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

Community
Advanced