/pstack:no-comments
AutoIn one lineCleans up comments before review, keeping only licenses, public API docs and notes on outside rules.
- When to use
- Before the code goes to review.
/pstack:no-comments the diffJust asking vs. using it
The same request, typed plainly or with /pstack:no-comments. Here's what changes.
With /pstack:no-commentsdo not remove comments in place.Offers a type, test or lint that enforces it, then deletes the comment once you approve.What the document says
2 sections, about 500 words, 2 min to read. Click a section to read it.
OpeningIt hands the comments to a fresh helper, Comment Sicko, defers to its view, and acts only on findings it accepts.
Wording worth borrowing
A few sentences from the original: what each one makes the AI do, why it works, and how you can borrow it.
Keep each rule in one place
Do not restate its rules.
- Makes the AI
- The main AI passes only the scope, not Comment Sicko's rules, so the two can't contradict each other.
- Why it works
- A rule written in one place is changed in one place, so two clashing versions never appear.
- Borrow it
- When you hand off a task, write: "Formatting rules are in the attached template. I won't repeat them here."
Make keeping need proof
A keep survives only with proof it is about something we cannot change.
- Makes the AI
- Comments are deleted by default. One stays only with proof it's about something outside our control.
- Why it works
- Requiring proof to keep tips the default toward deleting, so the AI doesn't keep everything when unsure.
- Borrow it
- When tidying files, say: "Archive old files by default. Keep one on the desktop only if you can say why it's needed next week."
Decide ties in advance
If a kill is ambiguous, do not restore.
- Makes the AI
- When it can't tell whether a deletion was right, it doesn't agonize. It follows the set direction.
- Why it works
- Settling ties ahead of time means the AI neither stops to ask nor judges differently each time.
- Borrow it
- When the AI sorts feedback, write: "If you can't tell a complaint from a suggestion, treat it as a complaint."
Split roles in two short lines
Architect shapes. Step 4 implements.
- Makes the AI
- The design step stops at a sketch. Changing the code waits for the next step.
- Why it works
- Two tiny sentences cut cleanly between who does what, so the AI won't edit code while designing.
- Borrow it
- For a long piece, say: "Step one: outline only. Step two: write."
Full text
The SKILL.md the AI reads, as written.
descriptionSpawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
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
- Spawn
Taskwithsubagent_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:Agentin Claude Code (subagent_type: general-purpose),taskin OpenCode (subagent_type: general),spawn_agentin Codex. Its prompt isreferences/comment-sicko.mdverbatim, 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. - Inspect its report and diff. Reject application-code edits, scope escapes, exception-protected deletions, misstated
MUST KILLreasons, 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 actionableMUST KILLs. Restore deletions only with exact exceptions and scoped proof. Before accepting thinIMPORTANTordo not removekills or keeps, run/pstack:howor/pstack:whyon their symbol. If a kill is ambiguous, do not restore. If a keep is refuted or still ambiguous, delete it, except aREVIEWkeep about an outside rule, which stays until someone checks that rule. Report it open. Revert and rerun one rejected report with the failure named. If you reject the rerun too, revert only its rejected findings, report them open, and go on with the accepted ones. - 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
/pstack:architectonce for the accepted set and surrounding code. Stop at the sketch. Architect shapes. Step 4 implements. - 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.
- Constraint comments say
do not remove,do not change wording, ortalk 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. - Report the deletion count, restored comments,
REVIEWkeeps, reruns, architect sketch, fixes, encoding offers, encodings, unenforced constraints, and other open work.
Original by Lauren Tan (poteto), MIT license. Checked against the pstack mirror at 97de40d. View on GitHub