Jak używać
- Skopiuj polecenie instalacji i sprawdź źródła przed instalacją we własnym środowisku agenta.
- W oryginale sprawdź wymagane narzędzia, dane dostępowe i obsługiwane środowiska.
- Opisz dane wejściowe i oczekiwany rezultat; porównaj wynik ze źródłami.
npx skills add https://github.com/aicodeking/deepseek-stack --skill ds-adoptPrzed rozpoczęciem
- Instalacja nie obejmuje subskrypcji modelu, limitu API ani uprawnień do plików.
- Gwiazdki i instalacje pokazują aktywność, a nie niezależny test jakości lub bezpieczeństwa.
Oryginalny dokument Skill
Treść z repozytorium z zachowaniem nagłówków, przykładów, kodu, tabel, linków i obrazów.
Finish someone else's work as if it were yours, but credit them for what they did.
Steps
- Read the source PR, branch or thread in full: description, commits, review comments and any later corrections from the user.
- Find the real current state: the head SHA, uncommitted changes and open review findings. Treat the handoff notes as hints, not facts.
- Write down the original goal in one sentence.
- Choose where to work. By default, make a new branch with the original commits on it and add your fixes as separate commits. Continue in place or stack only if the user asked for it.
- Run
ds-reviveto bring the work up to date with the base branch. - Fix what is needed to reach the original goal. Simplify where you can, but keep every intended behavior.
- Verify on your own. Reproduce the original problem, then show it fixed. Run the real workflow, not only mocked tests. Record the commands and output.
- Check the source PR again. It may have changed while you worked.
- If a PR is wanted, file it with
ds-pr, then watch it withds-watch-pr. Useds-pr-commentsfor any reply. - Report what you inherited, what you changed, how you verified it, how credit was kept and what is still open.
Stop when
- The goal is reached, verified and reported.
- The goal is unclear, or finishing it needs a product decision. Ask the user.
- Verification fails three times in a row on the same issue. Report the blocker.
Rules
- Keep the original Git authors and co-author trailers. Name the contributors and link the original PR in the description.
- If the PR will be squashed, keep human co-author lines in the squash message. Use verified identities only, never guessed emails.
- Do not defend the old code because it exists. Do not add unrelated features.
- Do not edit, merge or close the original PR without permission.
- State plainly what you could not verify.
