aicodeking/deepseek-stack

ds-adopt

Takes over an existing PR, branch or agent thread and finishes its original goal while keeping credit for the first contributors.

查看源码

使用方法

  1. 复制安装命令,在自己的智能体环境安装前先检查源码包。
  2. 从原始文档核对所需工具、凭据和支持的宿主。
  3. 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/aicodeking/deepseek-stack --skill ds-adopt

开始前需了解

  • 安装不包含模型订阅、API 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

Finish someone else's work as if it were yours, but credit them for what they did.

Steps

  1. Read the source PR, branch or thread in full: description, commits, review comments and any later corrections from the user.
  2. Find the real current state: the head SHA, uncommitted changes and open review findings. Treat the handoff notes as hints, not facts.
  3. Write down the original goal in one sentence.
  4. 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.
  5. Run ds-revive to bring the work up to date with the base branch.
  6. Fix what is needed to reach the original goal. Simplify where you can, but keep every intended behavior.
  7. 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.
  8. Check the source PR again. It may have changed while you worked.
  9. If a PR is wanted, file it with ds-pr, then watch it with ds-watch-pr. Use ds-pr-comments for any reply.
  10. 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.
来自同一仓库

更多 Skills

全部 Skills