aicodekingaicodeking/deepseek-stack/skills/ds-adopt/SKILL.md

ds-adopt

Skill80 starsChanged 15 days agoMITView on GitHub

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.

In this repository28 other files it gives its agents.
- ds-best-of-nSkill
- ds-blast-radiusSkill
- ds-blueprintSkill
- ds-catchupSkill
- ds-context-resetSkill
- ds-design-auditSkill
- ds-designSkill
- ds-explainSkill
- ds-helpSkill
- ds-jurySkill
- ds-ledgerSkill
- ds-lessonsSkill
- ds-modeSkill
- ds-plan-loopSkill
- ds-pr-commentsSkill
- ds-principlesSkill
- ds-prSkill
- ds-readySkill
- ds-review-loopSkill
- ds-reviveSkill
- ds-sharpenSkill
- ds-shipSkill
- ds-swarmSkill
- ds-tddSkill
- ds-unslopSkill
- ds-unstickSkill
- ds-verify-loopSkill
- ds-watch-prSkill

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 8 are distinctive, and 2 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific
could be automatic: a setting could enforce it

Distinctive:
Read the source PR, branch or thread in full: description, commits, review comments and any later corrections from the user.
line 10
Distinctive:
Write down the original goal in one sentence.
line 12
Very specific:
Run ds-revive to bring the work up to date with the base branch.
line 14
Distinctive:
Verify on your own. Reproduce the original problem, then show it fixed.
line 16
Distinctive:
Check the source PR again.
line 17
Very specific:
If a PR is wanted, file it with ds-pr, then watch it with ds-watch-pr.
line 18
Distinctive:
Keep the original Git authors and co-author trailers.
line 29
Distinctive:
If the PR will be squashed, keep human co-author lines in the squash message.
line 30
Distinctive:
Do not defend the old code because it exists.
line 31
Distinctive:
Do not edit, merge or close the original PR without permission.
line 32

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

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-revive to 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 with ds-watch-pr. Use ds-pr-comments for 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free