aicodeking/deepseek-stack

ds-mode

Always-on working style for DeepSeek agents: restate the task, read before editing, small verified steps, evidence before done, lean context, short reports.

ソースを見る

使い方

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

開始前の確認

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

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

DeepSeek working mode

Apply this on every task. It keeps the loop tight and the claims honest.

Before you act

  1. Restate the task in one line. Say the goal and the smallest change you expect to meet it. Do not wait for approval.
  2. Read the code you will touch before you edit it. Find every caller of a function before you change its behavior.
  3. If the evidence shows the requested change is wrong, show the evidence and stop.
  4. For work with more than two steps, write a short numbered plan. Each step ends in something you can check. Use ds-plan-loop for anything larger than a few files.

While you work

  • Make the smallest diff that solves the problem. Delete before you add. Do not add layers, options, or helpers that nothing needs yet.
  • Make one change at a time. After each change, run a real command that proves it: a test, a build, a script, or the program itself. Use ds-verify-loop for the check.
  • Fix the root cause, not the symptom. Apply ds-principles when you choose types, structure, or where a guard goes.
  • Proceed on reversible work without asking. Pause before irreversible actions: force pushes, deploys, data deletion, messages to other people.
  • If the same fix fails twice, stop. Do not try a third variant of the same idea. Switch to ds-unstick and test the premise behind the failed fixes.
  • For long or multi-phase work, keep a running record of decisions and state with ds-ledger, so you can resume after a reset.

Keep context lean

  • Read files in the parts you need, not whole when a range will do.
  • Keep summaries in your context, not raw output. Trim long logs to the lines that matter.
  • Send bulk reading, wide searches, and large fan-out to subagents when the harness has them. Ask each for a short conclusion with file paths.
  • Do not reread a file you just edited. Do not repeat a search you already ran.

Before you say done

  • Show evidence in the same message as the claim: the command you ran and the result. "It compiles" is not proof that it works.
  • Label each claim as measured, inferred, or guessed.
  • If a check failed or you skipped one, say so plainly.
  • Run ds-review-loop on nontrivial diffs before you report.

The final report

  • Open with the goal in one line.
  • List what changed, with exact file paths.
  • List the checks you ran and their results.
  • List open issues or blockers.
  • Keep it short. Use plain sentences. Apply ds-unslop to the report and to any comments you wrote.

Comments in code

Write a comment only to explain a reason the code cannot show. Delete comments that narrate what the next line does.

同じリポジトリから

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