⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
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.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
deepseek-stack
Skills that make DeepSeek models (V4.1 Flash, V4 Pro) work like a much more expensive model. Cheap models usually fail in the same few ways: they skip the plan, claim a fix works without running it, retry a broken idea over and over, and drift on long runs. Each skill here closes one of those gaps with a short loop, a hard stop condition and a demand for real evidence.
It works in any harness that reads SKILL.md files: Claude Code, Codex, Cline, OpenCode, PandaCode and others.
Install
npx skills add aicodeking/deepseek-stack
Add -g to install for every project. To install one skill only:
npx skills add aicodeking/deepseek-stack --skill ds-verify-loop
Manual install: copy skills/* into ~/.claude/skills/, ~/.codex/skills/ or your harness's skills folder.
Not sure where to start? Run /ds-help.
Skills
Core
| Skill | What it does |
|---|---|
ds-mode | Always-on working style: restate, read first, small verified steps, evidence before "done". |
ds-principles | 21 engineering rules of thumb, each with a trigger. |
ds-help | Picks the right skill for a task. |
Loops
| Skill | What it does |
|---|---|
ds-plan-loop | Plan with a check per step, critique once in a fresh pass, then build one step at a time. |
ds-verify-loop | Edit, run the real check, read the real error, fix the root cause. Max 5 rounds. |
ds-unstick | Same failure twice: name the shared assumption, test it, pick a different approach. |
ds-context-reset | Keep a PROGRESS.md and continue in a fresh context when the run gets long. |
ds-ledger | One row per decision for long or unattended runs, re-read before each step. |
ds-review-loop | Author plus fresh-context reviewer until both agree. Max 4 rounds. |
ds-jury | Reviews from two or three different models until they agree. |
ds-best-of-n | N parallel attempts, pick the best, graft in the strong parts of the rest. |
ds-swarm | Fan out parallel workers and merge their results into one report. |
Build
| Skill | What it does |
|---|---|
ds-sharpen | Restate the goal, make the task deeper, rewrite the prompt. |
ds-blueprint | Types, signatures and module layout first, then implement. |
ds-tdd | A failing test first, then the smallest fix. |
ds-blast-radius | Find what a change could break outside its diff and prove it is safe. |
ds-design | Build a frontend with a clear visual direction, not the generic AI look. |
ds-design-audit | Score an existing UI with evidence, fix the top problems, re-check. |
Ship
| Skill | What it does |
|---|---|
ds-pr | File a short PR that leads with the problem. |
ds-watch-pr | Watch CI and review bots, fix real findings. |
ds-ship | From change to merged PR, unattended. |
ds-ready | Same as ds-ship, but stops before the merge. |
ds-adopt | Finish someone else's PR or branch and keep their credit. |
ds-revive | Rebase an old PR, or decide it should be closed. |
ds-pr-comments | Format comments an agent posts for you. |
Understand
| Skill | What it does |
|---|---|
ds-explain | How code works and why it is built that way, in plain words. |
ds-catchup | What changed while you were away, and what is waiting on you. |
ds-lessons | Turn repeated agent mistakes into types, lints or tests. |
ds-unslop | Remove AI tells from prose and comments. |
Tips for DeepSeek
- Use thinking mode at max effort for planning and review. It matters more than any skill.
- Run big jobs at off-peak hours, when the API price is lower.
- DeepSeek is cheap, so spend tokens on quality:
ds-best-of-n,ds-review-loopandds-jurycost little and catch a lot. - Pair a stronger planner with DeepSeek as the implementer if your harness supports separate plan and act models.
Requirements
gh(GitHub CLI), signed in, for the Ship skills.python3fords-watch-pr/scripts/watch_pr.py.- Subagents or a second model for
ds-jury,ds-best-of-nandds-swarm. Without them, the skills run attempts one after another in fresh contexts.
License
MIT
// HOW IT'S BUILT
// FILES
2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
skills/ds-adopt/SKILL.md2.1 KB70b8d316e15cupstream ↗
--- 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.README.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/aicodeking-deepseek-stack-skills-ds-adopt.md