mcpField
N
no-comments

no-comments

github.com/q-qp-pTesting & quality144 installsUpdated 2w ago
Repository

About no-comments

no-comments is an agent skill for reviewing scoped code or diffs and removing comments judged unnecessary or misleading. It directs a comment-focused subagent review, specifies how to assess findings, and guides root-cause fixes and reporting.

Key features

  1. 01Review scoped files or diffs
  2. 02Delegate comment review to a subagent
  3. 03Validate findings and exceptions
  4. 04Apply minimal root-cause fixes
  5. 05Report deletions and open work

Use cases

  1. 01Auditing comments in a current diff
  2. 02Removing comments flagged by a focused review
  3. 03Handling constraints that require preserving comments

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/q-qp-p/pstack --skill no-comments

After installing, type/no-commentsin Claude Code to confirm it loaded.

Bundled filesreferences/comment-sicko.md

Details

From the project README

No comments

Spawn Comment Sicko. Act on accepted findings.

Defer to Comment Sicko's fresh perspective.

Scope

Use the caller's files or diff. Otherwise use the current diff against the base branch, default main, including the working tree.

Steps

  1. Spawn Task with subagent_type: "comment-sicko". Pass the scope. Pick each subagent's reasoning level and fast or standard speed for the job, per the Subagents section of the poteto-mode skill. Do not restate its rules. If your harness doesn't have comment-sicko registered as a subagent (any harness other than Cursor with the pstack plugin), spawn a general subagent instead: Agent in Claude Code (subagent_type: general-purpose), task in OpenCode (subagent_type: general), spawn_agent in Codex. Its prompt is references/comment-sicko.md verbatim, then the scope. If your harness has no subagent tool, as in Pi without an extension, run that prompt yourself in a fresh pass over the scope.
  2. Inspect its report and diff. Reject application-code edits, scope escapes, exception-protected deletions, misstated MUST KILL reasons, and flags that treat kept intentional code as guilty. Reshape flags on our-code surprises stay actionable. Do not restore those comments. A keep survives only with proof it is about something we cannot change. Audit missed scoped lint and TypeScript suppressions. Correctness or safety suppressions stay actionable MUST KILLs. Restore deletions only with exact exceptions and scoped proof. Before accepting thin IMPORTANT or do not remove kills or keeps, run /how or /why on their symbol. If a kill is ambiguous, do not restore. If a keep is refuted or still ambiguous, delete it. Revert and rerun one rejected report with the failure named. Reject a second, report it open, and fail /no-comments.
  3. Fix trivial accepted flags directly by deleting a dead path, dropping a parameter, or using the real API. If any fix needs a shape, run /architect once for the accepted set and surrounding code. Stop at the sketch. Architect shapes. Step 4 implements.
  4. Implement the smallest root-cause fix in scope. Remove every named workaround. If the root cause is out of scope, land the smallest in-scope fix and report the rest open. The principle-fix-root-causes and principle-redesign-from-first-principles skills guide intent only. Neither authorizes widening the fence nor fixing instances outside it. Never bolt on symptom guards.
  5. Constraint comments say do not remove, do not change wording, or talk to X before changing. Leave keeps about things we cannot change. Offer the cheapest in-scope type, runtime, test, or CI lint. Wait for interactive approval. Unattended and eval require caller pre-approval. If approved, encode then delete. Otherwise delete, report the constraint open, and sketch out-of-scope work.
  6. Report the deletion count, restored comments, reruns, architect sketch, fixes, encoding offers, encodings, unenforced constraints, and other open work.

Comments

Markdown supported