Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
npx skills add https://github.com/uzairansaruzi/p3-stack --skill no-comments
Spawn Comment Sicko. Act on accepted findings.
Defer to Comment Sicko's fresh perspective.
Use the caller's files or diff. Otherwise use the current diff against the base branch, default main, including the working tree.
delegate_task with mode: "async" and the judgment and prose model from orchestrator_capabilities. Its brief is the text of agents/comment-sicko.md plus the scope: file paths, or the diff itself. Do not restate its rules. The child sees only the brief, and it is read-only. Drain it with task_status.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. Rerun one rejected report with the failure named in a fresh delegate_task. Reject a second, report it open, and fail /no-comments./architect once for the accepted set and surrounding code. Stop at the sketch. Architect shapes. Step 4 implements.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 the user's approval in the thread. Unattended runs require caller pre-approval. If approved, encode then delete. Otherwise delete, report the constraint open, and sketch out-of-scope work.Take uzairansaruzi/no-comments from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.