使用方法
- 复制安装命令，在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物，并对照来源检查输出。
npx skills add https://github.com/aicodeking/deepseek-stack --skill ds-pr-comments开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况，不等于独立质量或安全测试。
仓库原始内容
按源仓库内容呈现，保留标题、案例、代码、表格、链接以及原文引用的演示图片。
Make every agent-written comment easy to spot, short and safe to publish.
Steps
- 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.
- 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.
- Scan the full comment, including quotes and attachments, for secrets, tokens, private paths and personal data. Remove them.
- Preview the final Markdown. Confirm the note and the reply render as two separate blocks.
- Post the comment.
- Confirm GitHub returned the comment or review URL. Print it.
- Resolve a review thread only after its reply posted.
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.
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.
