使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
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.
