aicodeking/deepseek-stack

ds-swarm

Fan out N parallel workers on slices of a job or on a race, collect every result, and return one evidence-backed report.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/aicodeking/deepseek-stack --skill ds-swarm

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

ds-swarm

Split work that is wide but shallow across parallel workers, then merge their proven results into one report.

Steps

  1. State the done condition and the report the swarm must return.
  2. Pick the shape. Partition the job into non-overlapping slices, or race N workers on the same brief, or both. For a race, decide up front how you will choose: first pass, rank all, or best one.
  3. Write one brief per worker that stands alone: goal, exact slice, how to verify, what to report. When workers test specific commits, name the exact commit hashes and the measurement method.
  4. Give every worker that writes files its own output location.
  5. Spawn all workers at once. If the harness cannot run subagents, run the briefs one by one in fresh contexts.
  6. Each worker reports PASS, ISSUES or BLOCKED with evidence: commands run and their output. ISSUES lists every provable issue, not just the first.
  7. Collect results. Reject any result with no evidence or the wrong commit and respawn that worker once. A second miss is a recorded gap, not a pass.
  8. Merge into one report: the verdict, each slice or arm with its evidence, gaps, and duplicates merged by root cause.

Stop when

  • Every slice has a result or a recorded gap and the report is written.
  • Or a race has a winner under the rule from step 2.
  • Never respawn a worker more than once.

Rules

  • Workers do not share writable state.
  • A missing slice is never counted as passing.
  • Report what workers proved, not what they claimed.
同じリポジトリから

関連する 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日