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 從公開儲存庫中收錄這些內容。

檢舉或申請下架