aicodeking/deepseek-stack

ds-pr-comments

Formats and posts GitHub comments written by an agent on the user's behalf, with clear attribution and no leaked secrets.

ソースを見る

使い方

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

  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.

  1. Scan the full comment, including quotes and attachments, for secrets, tokens, private paths and personal data. Remove them.
  2. Preview the final Markdown. Confirm the note and the reply render as two separate blocks.
  3. Post the comment.
  4. Confirm GitHub returned the comment or review URL. Print it.
  5. 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.
同じリポジトリから

関連する Skills

すべての Skills
aicodeking
コミュニティ

ds-adopt

Takes over an existing PR, branch or agent thread and finishes its original goal while keeping credit for the first contributors. Use when the user says take over, adopt, pick up or finish this PR, or /ds-adopt.

1時間の導入数
2
GitHub Stars
75
更新日
10月28日
aicodeking
コミュニティ

ds-best-of-n

Run N independent attempts at the same task in parallel, pick the strongest as the base, and graft the best parts of the others into it. Use when one attempt at a non-trivial artifact could land on the wrong shape, or for /ds-best-of-n, 'try a few versions', 'best of 3'.

1時間の導入数
2
GitHub Stars
75
更新日
10月28日
aicodeking
コミュニティ

ds-blast-radius

Find what a change could break outside its own diff, then prove the key safety fact by running real code. Use before shipping a risky or untrusted change, for 'what could this break', 'blast radius of X', or /ds-blast-radius.

1時間の導入数
2
GitHub Stars
75
更新日
10月28日
aicodeking
コミュニティ

ds-blueprint

Design the types, function signatures and module layout first, agree on that shape, then implement against it. Use when work is non-trivial and coding straight away would lock in the wrong structure, or for /ds-blueprint, 'design this first', 'architect this'.

1時間の導入数
2
GitHub Stars
75
更新日
10月28日