no-comments

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

No comments

无注释

Spawn Comment Sicko. Act on accepted findings.

Authoring agents defend comments. Defer to Comment Sicko's fresh perspective.

生成Comment Sicko。根据已接受的问题采取行动。

编写代理负责维护注释。听从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.

使用调用者提供的文件或差异。否则，使用当前与基准分支（默认

main

）的差异，包括工作树。

Steps

步骤

Spawn
```
Task
```
with
```
subagent_type: "Comment Sicko"
```
. Pass the scope. Do not restate its rules.
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 KILL
```
s. 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
```
.
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.
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: fix real causes, redesign as if requirements always existed, never bolt on symptom guards. Neither authorizes widening the fence nor fixing instances outside it.
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.
Report the deletion count, restored comments, reruns, architect sketch, fixes, encoding offers, encodings, unenforced constraints, and other open work.

生成
```
Task
```
，设置
```
subagent_type: "Comment Sicko"
```
。传递范围信息。无需重述其规则。
检查其报告和差异。拒绝应用代码编辑、范围越界、受异常保护的删除、错误陈述的
```
MUST KILL
```
理由，以及将保留的有意代码标记为违规的标识。针对我们代码中意外情况的标识需保持可执行性。不要恢复这些注释。只有在有证据表明注释涉及我们无法更改的内容时，才保留该注释。检查遗漏的范围内lint和TypeScript抑制。正确性或安全性相关的抑制仍需作为可执行的
```
MUST KILL
```
项处理。仅在有明确例外和范围内证据的情况下，才恢复删除的内容。在接受简单的
```
IMPORTANT
```
或
```
do not remove
```
删除或保留操作之前，对其符号运行
```
/how
```
或
```
/why
```
命令。如果删除操作不明确，则不恢复内容。如果保留操作被反驳或仍不明确，则删除该注释。回退并重新运行一次被拒绝的报告，并注明失败原因。如果第二次仍被拒绝，则将其报告为未解决问题，并终止
```
/no-comments
```
命令。
通过删除死路径、移除参数或使用真实API直接修复已接受的微小问题。如果任何修复需要架构设计，针对已接受的问题集及周边代码运行一次
```
/architect
```
命令。仅停留在草图阶段。由架构师设计方案。步骤4负责实现。
在范围内实施最小的根本原因修复。移除所有已标记的临时解决方案。如果根本原因超出范围，则实施范围内最小的修复，并将剩余问题报告为未解决。principle-fix-root-causes和principle-redesign-from-first-principles技能仅用于指导意图：修复真正的原因，从头开始重新设计（仿佛需求一直存在），绝不添加针对症状的防护措施。这两项技能均不允许扩大修复范围或修复范围外的问题实例。
约束性注释包含
```
do not remove
```
、
```
do not change wording
```
或
```
talk to X before changing
```
等内容。保留那些涉及我们无法更改内容的注释。提供范围内成本最低的类型检查、运行时检查、测试或CI lint方案。等待交互式批准。无人值守和评估场景需要调用者预先批准。如果获得批准，则进行编码并删除注释。否则，删除注释，将该约束报告为未解决问题，并草拟范围外的工作内容。
报告删除数量、恢复的注释、重新运行次数、架构草图、修复内容、编码方案提议、已实施的编码、未强制执行的约束以及其他未解决的工作。