no-comments
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseNo comments
无注释
Remove comments that repeat the code or preserve dead code. Leave a working change, with useful explanations intact.
Use the supplied paths or diff. Otherwise inspect the diff against the base branch, including staged and unstaged changes. Change comments only unless code changes are also requested.
Read the surrounding code before deleting a comment. Remove narration, section banners, and commented-out implementations. Do not replace them with shorter narration.
Keep required legal headers, public API contracts, and explanations of constraints the code cannot express. A dependency workaround, protocol requirement, or issue link can explain why apparently simpler code would be wrong. Investigate uncertain comments before deciding.
Treat lint directives, type suppressions, compiler annotations, and generated-file markers as behavior. Remove them only when the affected checks still pass. If removing one requires an out-of-scope code fix, preserve it and identify the exact symbol and reason.
When code changes are authorized, use a clear name, type, or small refactor to remove the need for an explanation. Otherwise report unclear code without inserting warning tags or knowingly breaking validation.
Review the diff for accidental code changes. Run affected checks when comments influence tooling or execution. Report what changed and any concrete follow-up; do not ask the user to approve routine deletions before doing the work.
删除重复代码含义或用于保留死代码的注释。保持更改可正常工作,并保留有用的说明。
使用提供的路径或 diff。否则,检查 diff 相对于基准分支的变化,包括已暂存和未暂存的更改。除非同时要求修改代码,否则仅修改注释。
删除注释前先阅读周边代码。移除叙述性注释、章节横幅和被注释掉的实现。不要用更简短的叙述性注释替换它们。
保留必要的法律声明头、public API 契约,以及对代码无法表达的约束的解释。依赖项的 workaround、协议要求或 issue 链接可以解释为何看似更简单的代码实际上是错误的。决定前,应调查含义不明确的注释。
将 lint directives、type suppressions、compiler annotations 和 generated-file markers 视为与行为相关的内容。仅在相关检查仍能通过时移除它们。如果移除某项需要修改范围外的代码,则保留该项,并指出确切的 symbol 和原因。
获得代码更改授权时,使用清晰的名称、类型或小型重构来消除添加说明的必要性。否则,应报告含义不明确的代码,不要插入警告标签,也不要故意破坏验证。
检查 diff 中是否有意外的代码更改。当注释会影响工具处理或执行时,运行相关检查。报告所做的更改及任何具体后续事项;不要在执行常规删除前请求用户批准。