사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
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
- 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.
