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.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- 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.
03 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-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.
Greeneek working contract
This skill is installed in the Greeneek repository. Where a step below conflicts with these rules, these rules win.
- Restate the goal in one line, read the real files before editing, and work on
mainin small vertical slices. Preserve uncommitted and concurrent work; never reset, force-push, or overwrite another session's changes. - Evidence before "done": run the real check and record the exact command and its output. Never weaken a test, add a blind retry, raise a timeout without a diagnosed cause, or delete a failing assertion to get green.
- Agent waves never commit, push, tag, or publish. No npm auto-publish on
main; release tags are immutable and Item 8 stays last. - Live model lanes stay BLOCKED without
GREENEEK_API_KEY; mocked coverage is never reported as real-CLI verification. - Registrations are effects, ESM everywhere, and misconfiguration fails at the earliest resolvable point.
- Source of truth:
.agents/notes/proposed/process/2026-11-01-v0.3.9-master-release-plan.md. Append evidence to its Execution ledger and keep its Resume State current in the same commit as the change.
Greeneek-specific override
The master release plan is the handoff, and its "do not assume previous notes are accurate" rule is literal. Verify HEAD, git status, branches, concurrent writers, and the runner verdict before acting. Never discard user changes or another agent's uncommitted work.
04 同仓库更多 Skills
user-only-skill
Prove model-disabled skills stay outside the model catalog.
snapshot-skill
Exercise project skill discovery and loading in snapshot tests.
model-only-skill
Prove user-disabled skills remain available to the model.
editing-cordis-compositions
Use when creating, changing, or validating a Cordis composition for this harness — writing or editing an agent preset, adding or removing a plugin row, deciding whether something belongs to the host composition or to one session, checking whether a preset you authored actually mounts, or diagnosing a row that mounted but contributed nothing.
cordis-plugin-development
Create, modify, debug, or extend dynamic Cordis Plugins, including Host Services and Events, Client Slot and theme UI, Package-private Client-to-Host calls, dynamic Tools, version updates, approval failures, and runtime diagnostics. Use this Skill to route a user request to the correct platform and Inspect Provider, then define, run, repair, or roll back the Plugin.
preview-tour
Inspect the bundled Preview workspace and its deterministic Session examples.