aicodeking/deepseek-stack

ds-ledger

Keep a one-row-per-decision log during long or unattended runs, and re-read it before each step so the run does not drift from its goal.

ソースを見る

使い方

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

開始前の確認

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

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

ds-ledger

A long run forgets its own reasons. A short written ledger keeps the goal in view and lets a reviewer trust the result.

Steps

  1. Create one TSV file, for example .ds-ledger.tsv, with the header ts phase decision why evidence result. Put the goal and done condition in the first row.
  2. Before each step, re-read the goal row and the last ten rows. Check that the next step still serves the goal. If it does not, log the drift and correct course.
  3. After each real decision, append one row:
  • ts: ISO 8601 time.
  • phase: the phase or workstream.
  • decision: what you chose or did, one line.
  • why: the reason in plain words.
  • evidence: a pointer, never prose. A commit hash, file:line, a command and its result, or an artifact path.
  • result: the outcome, such as "tests pass", "reverted", "open".
  1. Keep each cell on one line with no tabs.
  2. Log reverts and dropped work too, with the reason. Failures are the most useful rows.
  3. At the end, add a summary row and point the user to the file. Commit it only if a reviewer needs it.

Stop when

  • The run ends and the summary row is written.
  • If three rows in a row show no progress toward the goal, stop the run and report.

Rules

  • Every row needs evidence you can open or rerun. "Looked fine" is not evidence.
  • Write rows the way you would tell a teammate, plain and concrete.
  • Do not rewrite old rows. Append corrections.
同じリポジトリから

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