no-comments
Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
How do I install this agent skill?
npx skills add https://github.com/backnotprop/pstack --skill no-commentsIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The 'Comment Sicko' skill is an administrative utility for code comment auditing and management. It performs local file and diff analysis without making network requests, downloading remote code, or seeking elevated permissions. No malicious patterns or security risks were identified during the analysis.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
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. 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/howor/whyon 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. - 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
/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, reruns, architect sketch, fixes, encoding offers, encodings, unenforced constraints, and other open work.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/backnotprop/pstack/no-comments">View no-comments on skillZs</a>