mcpField
N
no-comments

no-comments

github.com/hachejDevelopment160 installsUpdated 3d ago
Repository

About no-comments

A code-review skill that delegates comment and suppression findings to the Comment Sicko subagent, then guides maintainers through evaluating reports and making scoped fixes. It emphasizes root-cause changes and reporting unresolved issues.

Key features

  1. 01Delegate review to Comment Sicko
  2. 02Inspect findings against the diff
  3. 03Reject out-of-scope changes
  4. 04Fix accepted issues at root cause
  5. 05Report fixes and open work

Use cases

  1. 01Review comments in a change set
  2. 02Audit lint and TypeScript suppressions
  3. 03Remove actionable comments within scope

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/hachej/boring-stack --skill no-comments

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

Bundled filesLICENSEreferences/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. Do not restate its rules.
  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