no-comments

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

No comments

无注释

Spawn Comment Sicko. Act on accepted findings.

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.

使用调用方提供的文件或 diff。否则，使用当前工作树相对于基础分支（默认

main

）的 diff。

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. Neither authorizes widening the fence nor fixing instances outside it. Never bolt on symptom guards.
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.

以
```
subagent_type: "Comment Sicko"
```
启动
```
Task
```
。传递范围。不要复述其规则。
检查其报告和 diff。拒绝对应用代码的修改、越界操作、违反既定例外的删除、对
```
MUST KILL
```
理由的错误陈述，以及把有意保留的代码视为问题的标记。针对我们代码中意外之处提出重塑的标记仍应保持可执行。不要恢复这些注释。只有能够证明保留项涉及无法更改的内容时，它才可继续保留。审计范围内遗漏的 lint 和 TypeScript 抑制项。涉及正确性或安全性的抑制项仍应作为可执行的
```
MUST KILL
```
。只有在存在明确例外且有范围内证据时，才恢复已删除的注释。在接受理由薄弱的
```
IMPORTANT
```
或
```
do not remove
```
型删除或保留判定之前，针对其符号运行
```
/how
```
或
```
/why
```
。如果删除判定存在歧义，不要恢复已删除的注释。如果保留判定被驳斥或仍有歧义，则删除相应注释。对于第一份被拒绝的报告，撤销相关修改，明确指出失败原因后重新运行。如果第二份报告仍被拒绝，则将其作为未解决项报告，并让
```
/no-comments
```
失败。
直接修复已接受标记所指的简单问题：删除无效代码路径、移除参数，或改用实际的 API。如果任何修复需要确定结构形态，针对已接受的一组修复及其周边代码运行一次
```
/architect
```
。到草图阶段即停止。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。等待交互式批准。无人值守运行和 eval 需要调用方预先批准。如果获批，先将该约束编码，再删除注释。否则，删除该注释，将该约束报告为未解决项，并勾勒范围外的工作方案。
报告删除的注释数量、已恢复的注释、重新运行情况、Architect 草图、各项修复、编码方案提议、已完成的编码、未强制执行的约束以及其他未解决工作。