No Comments

作者 cursorccb5507cec15無授權條款10K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫今天更新

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

AI 產生的概覽

啟動 Comment Sicko 子代理審查程式碼註解,修復已接受的發現,並為限制條件提供 lint 編碼方案。

功能
此技能編排一套審查流程,針對呼叫端提供的檔案或相對於基礎分支的目前 diff 啟動名為 Comment Sicko 的子代理。它會檢查子代理的報告,拒絕無效的編輯、刪除或標記,並直接修復簡單的已接受發現。對於限制條件類註解,它會提供範圍內成本最低的型別、執行階段、測試或 CI lint 編碼方案,並在編碼與刪除前等待互動式核准。最後報告刪除數量、還原的註解、重跑、修復、編碼提議以及未完成的工作。
適用情境
當你想要清理或刪除檔案集或 diff 中不必要的程式碼註解,並需要對保留或刪除哪些註解進行結構化審查時使用。它適合需要將限制條件類註解替換為可執行的 lint、型別、執行階段、測試或 CI 檢查的工作流程。它面向互動式使用,無人值守或評測執行需要呼叫端預先核准。
執行需求
僅以指令形式執行,不附帶指令碼。它需要能夠啟動型別為 Comment Sicko 的 Task 子代理,並能存取呼叫端的檔案或相對於基礎分支(預設 main)的 git diff。它引用了 /how、/why 和 /architect 命令以及 principle-fix-root-causes 和 principle-redesign-from-first-principles 技能,編碼限制條件時需要互動式核准。

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.
  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.

來源與署名

來源:cursor/plugins位於pstack/skills/no-comments提交ccb5507

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架