Back to Details

ds-pr-comments

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
Make every agent-written comment easy to spot, short and safe to publish.
确保每条由 Agent 撰写的评论都易于识别、简短且可安全发布。

Steps

步骤

  1. Write the reply. Lead with the conclusion. Cite the code line, check, test or reproduction that supports it. Mark what you verified and what is your opinion.
  2. Put this note at the top, with the reply below it:
    md
    > [!NOTE]
> **<model> responding on behalf of <user>**

Reply text starts here.
    Use the model name the harness reports. If it reports none, use the harness name. Use the user's name or GitHub login.
  3. Scan the full comment, including quotes and attachments, for secrets, tokens, private paths and personal data. Remove them.
  4. Preview the final Markdown. Confirm the note and the reply render as two separate blocks.
  5. Post the comment.
  6. Confirm GitHub returned the comment or review URL. Print it.
  7. Resolve a review thread only after its reply posted.
  1. 撰写回复。先给出结论。引用支持该结论的代码行、检查、测试或复现步骤。明确标注哪些内容已经验证，哪些内容只是你的判断。
  2. 将以下说明放在顶部，并在下方附上回复：
    md
    > [!NOTE]
> **<model> responding on behalf of <user>**

Reply text starts here.
    使用 harness 报告的模型名称。如果 harness 未报告模型名称，则使用 harness 名称。使用用户的姓名或 GitHub 登录名。
  3. 扫描完整评论，包括引用内容和附件，检查是否包含密钥、令牌、私有路径或个人数据，并将其移除。
  4. 预览最终的 Markdown。确认说明和回复呈现为两个独立区块。
  5. 发布评论。
  6. 确认 GitHub 已返回评论或审查 URL，并将其输出。
  7. 仅在回复发布成功后解决 review 线程。

Stop when

停止条件

  • GitHub returned a URL for each comment you meant to post.
  • A post fails twice. Report the error and do not resolve the thread.
  • GitHub 已为每条需要发布的评论返回 URL。
  • 发布连续失败两次。此时报告错误，并且不要解决该线程。

Rules

规则

  • Use the note on top-level comments, inline review comments, replies to bots and people, and dismissal reasons.
  • Do not use it in PR descriptions, commit messages or text the user asked to post word for word.
  • One attribution only. No signature, footer, heading or horizontal rule.
  • No thanks, filler or status updates such as "still working on it".
  • Never guess the model name.
  • 顶层评论、行内审查评论、对机器人或其他用户的回复，以及驳回原因，都必须使用该说明。
  • 不要在 PR 描述、commit message 或用户要求逐字发布的内容中使用该说明。
  • 只能添加一次来源说明。不要添加签名、页脚、标题或水平分隔线。
  • 不要使用致谢、无效填充内容或“still working on it”之类的状态更新。
  • 绝不猜测模型名称。