ds-adopt — Claude Code skill: take over unfinished work
ds-adopt — a Claude Code skill takes over an existing PR, branch, or agent thread and completes its original goal. It activates when asked to adopt or finish someone else’s work.
MIT 534 installs ★ 320 updated 2026-10-28
npx skills add aicodeking/deepseek-stack --skill ds-adopt -a claude-codeWhat ds-adopt does
The skill reads the PR, branch, or thread, including its commits, review notes, and later user corrections. It checks the current Git state, records the original goal, then chooses where to continue. By default, it creates a new branch from the original commits and adds fixes in separate commits. It uses ds-revive to update the work against the base branch.
The skill runs the original workflow to verify the fix and records the commands and output. If a PR is requested, it files one with ds-pr, monitors it with ds-watch-pr, and uses ds-pr-comments to reply to comments. The original PR must remain untouched unless the user authorizes changes, a merge, or closure. If the goal is unclear, the skill asks; after three consecutive verification failures on the same issue, it reports the blocker.
What it helps with
- finish an inherited PR while preserving its original goal
- inspect a branch’s current state and outstanding review findings
- verify a fix by running the original workflow
- keep the original contributors’ credit in commits and PRs
Example prompts for the agent
- Take over this PR, finish its original goal, and preserve contributor credit.
- Pick up this branch, check its current state, and complete the original work.
- Adopt this agent thread and verify the fix with the original workflow.
How to install ds-adopt
1Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-adopt -a claude-code2Manually: put the files in place
~/.claude/skills/ds-adopt/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ds-adopt/
1Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-adopt -a codex2Manually: put the files in place
.agents/skills/ds-adopt/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-adopt -a cursor2Manually: put the files in place
.cursor/skills/ds-adopt/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aicodeking/deepseek-stack skills/ds-adopt2Manually: put the files in place
.github/skills/ds-adopt/SKILL.md1Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-adopt -a gemini-cli2Platform CLI
gemini skills install https://github.com/aicodeking/deepseek-stack --path skills/ds-adoptManually: put the files in place
.devin/skills/ds-adopt/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-adopt -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about ds-adopt
How do I install ds-adopt in Claude Code?
Run npx skills add aicodeking/deepseek-stack --skill ds-adopt -a claude-code. The skill file is at ~/.claude/skills/ds-adopt/SKILL.md.
What does ds-adopt do?
It takes over an existing PR, branch, or agent thread, works toward its original goal, and verifies the result. It preserves credit for the initial contributors.
Can ds-adopt edit or close the original PR?
No. It must not edit, merge, or close the original PR unless the user gives permission.
Source text
SKILL.md · MIT
--- name: ds-adopt description: "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." --- 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.
© aicodeking · MIT · aicodeking/deepseek-stack