Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

no-comments

别留废话注释：交给 Comment Sicko

Spawn Comment Sicko. Act on accepted findings.

Spawn Comment Sicko。对已接受的发现动手。

Defer to Comment Sicko’s fresh perspective.

听 Comment Sicko 的新鲜视角。

Scope

范围

Use the caller’s files or diff. Otherwise use the current diff against the base branch, default main, including the working tree.

优先用调用方给的文件或 diff。否则用相对 base 分支（默认 main）的当前 diff，含 working tree。

Steps

步骤

  1. Spawn Task with subagent_type: "Comment Sicko". Pass the scope. 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 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.

  7. Spawn Task，subagent_type: "Comment Sicko"。传入范围。别重复说它的规则。

  8. 检查它的报告和 diff。拒绝：改应用代码、越界、受例外保护的删除、MUST KILL 理由说错、把故意保留的代码当罪证的 flag。对我们代码里意外形状的 reshape flag 仍可执行——别恢复那些注释。keep 只有在证明「我们改不了的事」时才成立。审计漏掉的 scoped lint 和 TypeScript suppression。正确性/安全类 suppression 仍是可执行的 MUST KILL。恢复删除必须有精确例外和范围内证明。接受单薄的 IMPORTANT / do not remove 的 kill 或 keep 前，先对符号跑 /how 或 /why。kill 含糊就别恢复；keep 被推翻或仍含糊就删。回滚并带上失败原因重跑一份被拒报告。第二次再拒就标 open，并 fail /no-comments。

  9. 琐碎且已接受的 flag 直接修：删死路径、去掉参数、或用真 API。若需要定形状，对已接受集合及周边代码跑一次 /architect。停在 sketch。Architect 定形，Step 4 实现。

  10. 在范围内做最小根因修复。去掉点名的每个 workaround。根因在范围外：落地范围内最小修复，其余标 open。principle-fix-root-causes 和 principle-redesign-from-first-principles 只指导意图；都不授权扩篱笆或修范围外实例。绝不钉症状防护。

  11. 约束注释写着 do not remove、do not change wording 或 talk to X before changing。我们改不了的 keep 留下。提出范围内最便宜的 type / runtime / test / CI lint。等交互批准。无人值守和 eval 要调用方预批。批了就编码再删；否则删掉，约束标 open，并草拟范围外工作。

  12. 汇报：删除数、恢复的注释、重跑、architect sketch、修复、编码提议、已编码项、未强制的约束、以及其他 open 工作。