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 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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

모든 Skills
aicodeking
커뮤니티

ds-best-of-n

Run N independent attempts at the same task in parallel, pick the strongest as the base, and graft the best parts of the others into it. Use when one attempt at a non-trivial artifact could land on the wrong shape, or for /ds-best-of-n, 'try a few versions', 'best of 3'.

1시간 설치 수
2
GitHub Stars
75
업데이트
10월 28일
aicodeking
커뮤니티

ds-blast-radius

Find what a change could break outside its own diff, then prove the key safety fact by running real code. Use before shipping a risky or untrusted change, for 'what could this break', 'blast radius of X', or /ds-blast-radius.

1시간 설치 수
2
GitHub Stars
75
업데이트
10월 28일
aicodeking
커뮤니티

ds-blueprint

Design the types, function signatures and module layout first, agree on that shape, then implement against it. Use when work is non-trivial and coding straight away would lock in the wrong structure, or for /ds-blueprint, 'design this first', 'architect this'.

1시간 설치 수
2
GitHub Stars
75
업데이트
10월 28일
aicodeking
커뮤니티

ds-catchup

Give the user a short plain-language catch-up on what changed since their last message, followed by every decision still waiting on them. Use when the user returns after a long or unattended run, asks 'where are we', 'what did I miss', or types /ds-catchup.

1시간 설치 수
2
GitHub Stars
75
업데이트
10월 28일