← ClaudeAtlas

no-commentslisted

Use before review when the user asks to strip, remove, or clean up comments in code.
painhardcore/pstack · ★ 1 · Code & Development · score 72
Install: claude install-skill painhardcore/pstack
# No comments Spawn comment-sicko. Act on accepted findings. Authoring agents defend comments. Defer to comment-sicko's fresh perspective. If the `comment-sicko` agent is unavailable (a host without the agents mirror, such as Opencode before `.opencode/agents/` is in place), do not fail: perform the review inline. Read the scope, apply the same flag rules below, and report findings yourself. The agent is a convenience, not a prerequisite. ## 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. Use the host's native agent mechanism to run `comment-sicko` with the scope. If that agent is unavailable or delegation is forbidden, apply its rules inline. 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 KILL`s. 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