mcpField
N
no-comments

no-comments

github.com/mariusflorescuDevelopment1264 installsUpdated 3d ago
Repository

About no-comments

no-comments is a code-review skill that delegates comment review to a subagent called Comment Sicko, then applies accepted findings within the specified file or diff scope. It includes checks for suppressions, constraints, and the reporting of fixes and open work.

Key features

  1. 01Delegates review to Comment Sicko
  2. 02Reviews caller-provided files or diffs
  3. 03Checks accepted findings against scope
  4. 04Audits lint and TypeScript suppressions
  5. 05Reports fixes and unresolved work

Use cases

  1. 01Reviewing comments in a code diff
  2. 02Removing actionable problematic comments
  3. 03Checking scoped lint suppressions
  4. 04Tracking review findings and remaining work

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/mariusflorescu/pstack-t3 --skill no-comments

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

Bundled filesagents/openai.yamlreferences/comment-sicko.md

Details

From the project README

No comments

A skill named in bold or in backticks, or run as /<name>, is the file ../<name>/SKILL.md beside this skill's directory, and a principle named without its prefix is ../principle-<name>/SKILL.md. Read the file and follow it. Most pstack skills are user-only, so your skill tool cannot load them. Every delegate_task call follows the defaults in the Subagents section of ../poteto-mode/SKILL.md.

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 a delegate_task child titled Comment Sicko on your judgment and prose model from ~/.config/pstack/pstack-models.md (the parent model when the file or line is missing). Its brief starts with references/comment-sicko.md pasted verbatim, then the absolute paths of the how and why SKILL.md files with "Before you run /how or /why, read that SKILL.md in full and follow it", then 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.
  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 in a fresh delegate_task 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