aicodeking/deepseek-stack

ds-catchup

Give the user a short plain-language catch-up on what changed since their last message, followed by every decision still waiting on them.

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-catchup

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.

ds-catchup

Bring the user back up to speed in a minute, and hand them every call only they can make.

Steps

  1. Keep this turn read-only. Do not change code, start jobs or post anything.
  2. Collect what happened since the user's last message: your own work, subagent reports, and messages from others. Tool notifications are not user messages.
  3. Check the current state of anything touched: tests, branches, PRs, running jobs. Use fresh command output, not memory. Fix any number that does not match the source and say you fixed it.
  4. Write what changed in under 100 words. Say what it means for the user, for example "the login bug is fixed and its test passes". Leave out hashes, paths and commands unless the user needs one to act.
  5. List decisions waiting on the user. A decision is something only they can do: a product choice, an approval, an irreversible action, or access you lack. Include old ones still open. For each give: what it changes, the evidence, the risk, your recommendation, and "unknown" for missing facts.
  6. If nothing waits on them, say so plainly.

Stop when

  • The catch-up and the decision list are written. One reply, no follow-up work.

Rules

  • Never invent a decision to fill the list.
  • Work you can still do yourself is not a decision for the user.
  • Name things the way the user would, not by internal labels.
  • Short sentences, no jargon.
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.