aicodeking/deepseek-stack

ds-unstick

Break out of a repeating failure: name the assumption behind all the failed fixes, test it directly, list three other approaches, pick one, and restart clean if needed.

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

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

When two fixes fail the same way, the problem is usually a wrong belief, not a wrong edit. Find that belief and test it.

Steps

  1. Stop editing. Do not try a third variation of the same fix.
  2. Write down each failed attempt in one line: what you changed and what happened. Include the exact error text.
  3. Write the assumption that all of those attempts shared. Typical examples: "this file is the one that runs", "the config is loaded", "the function receives a string", "the cache is cleared", "the error comes from my code". Name one, in one sentence.
  4. Test that assumption directly with the cheapest probe that gives a yes or no answer: a print statement, a log line, a which or --version, a grep for the real call site, a minimal script, or a read of the docs for the exact version installed. Paste the result.
  5. If the assumption is false, you have found the real problem. Plan the fix from the new fact.
  6. If the assumption holds, list 3 different approaches. "Different" means another mechanism, library, layer or data path, not a tweak of the same edit. Give each approach one line on cost and risk.
  7. Pick one approach and say why in one sentence.
  8. Restart from a clean state if the failed attempts left debris: revert them with git (git stash or git checkout -- <files>), then apply only the chosen approach.
  9. Record the false assumption or the chosen approach in PROGRESS.md (see ds-context-reset) so a later session does not repeat the attempts.
  10. Return to ds-verify-loop with the new approach.

Stop when

  • The probe in step 4 explains the failure, or the new approach passes its check.
  • Two rounds of this skill have failed. Stop and report to the user: the attempts, the assumptions you tested, and the evidence. Ask for direction.

Rules

  • Do not repeat a fix that has already failed, even with small changes.
  • Evidence beats reasoning. If a probe takes a minute, run it.
  • Keep the failed-attempt list, because it is the most useful part of the report.
  • Use a clean state before a new approach, so that old edits cannot hide the result.
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.