No Comments

作者 backnotprop3a604672c46c无许可证1.3K 个星标收录于 2026年10月8日更新于 2026年10月8日仓库今天更新

Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.

AI 生成的概览

通过启动审查子代理来删除无依据的代码注释,修复被接受的发现,并为约束提供编码方案。

功能
该技能对调用方提供的文件或当前相对基线分支的差异执行一轮审查。它会启动 Comment Sicko 子代理(或通用子代理,或直接运行该提示词)来标记注释,然后检查报告与差异以驳回无效发现。它以最小的根因改动修复被接受的发现,并在删除前提出将声称的约束编码为类型、运行时、测试或 CI lint 检查。最后报告删除数量、恢复的注释、重跑、修复、编码提议和未完成工作。
适用场景
当代码库或差异中存在可能已失效、误导或无依据的注释,并希望对其进行审查和删除时使用。它适用于有独立审查子代理可用,或可直接运行该提示词的工作流。由于约束编码需要批准,它面向交互式使用。
运行要求
需要具备子代理工具(Task、Agent、task 或 spawn_agent)的代理运行环境,或能够直接运行所引用的提示词。它会读取 references/comment-sicko.md,并可能调用 /how、/why 和 /architect 命令。它不附带脚本,除代理本身外不需要凭据或网络访问。

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

  1. Spawn Task with subagent_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: Agent in Claude Code (subagent_type: general-purpose), task in OpenCode (subagent_type: general), spawn_agent in Codex. Its prompt is references/comment-sicko.md [blocked] verbatim, 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.
  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.

来源与署名

来源:backnotprop/pstack位于skills/no-comments提交3a60467

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架