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.

Ver código-fonte

Como usar

  1. Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
  2. Consulte no original as ferramentas, credenciais e ambientes necessários.
  3. Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/aicodeking/deepseek-stack --skill ds-mode

Antes de começar

  • A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
  • Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

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.

do mesmo repositório

Mais Skills

Todos os Skills
aicodeking
Comunidade

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.

Instalações / 1h
2
GitHub Stars
75
Atualizado
28 de out.
aicodeking
Comunidade

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'.

Instalações / 1h
2
GitHub Stars
75
Atualizado
28 de out.
aicodeking
Comunidade

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.

Instalações / 1h
2
GitHub Stars
75
Atualizado
28 de out.
aicodeking
Comunidade

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'.

Instalações / 1h
2
GitHub Stars
75
Atualizado
28 de out.