사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/aicodeking/deepseek-stack --skill ds-revive시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Update the idea, not only the branch. A clean rebase does not prove the PR still belongs.
Steps
- Fetch the latest base, the PR head and any related branches.
- Record the PR URL, state, base, head branch, head SHA, author, checks and review state. Read the title, body, linked issues, commits, threads and full diff.
- Write the PR's goal in one sentence.
- Find the merge base. Read what landed on the base branch since then. Search merged and open PRs for the same problem.
- Answer each question with evidence (commit, PR or file path):
- Has this problem already been solved?
- Did the APIs, types, schemas or structure it relies on change?
- Was the code it edits moved, deleted or simplified?
- Would landing it bring back old behavior or make two ways to do one thing?
- Is the benefit still worth the upkeep?
- Pick one verdict:
- REVIVE: goal and shape still fit. Go to step 7.
- REWORK: goal fits, shape does not. Describe the smallest rewrite and stop, unless the user also asked for the rework.
- CLOSE: superseded or no longer worth it. Cite the evidence and stop. Do not close it yourself.
- For REVIVE: work in a clean worktree at the recorded head. Rebase onto the fresh base. Resolve conflicts by the PR's goal and the base's newer rules.
- Run
git range-diffon the old and new series. Confirm no intended change was lost and nothing already landed came back. - Run the focused checks for the touched area. Mark each failure as real, pre-existing or infrastructure.
- Push with
--force-with-lease=<branch>:<old head SHA>. - Report the verdict first, then base changes, conflicts, push result, checks and the remaining decision with the PR link.
Stop when
- The report is written after any of the three verdicts.
- A conflict shows a product or design disagreement. Stop and reconsider the verdict.
- The lease fails. Fetch again and redo steps 4 to 6 once. If it fails again, report.
Rules
- Treat a dirty worktree as the user's. Never stash or discard it.
- Never merge, close or change the base branch. Never force-push without a lease.
- No conflicts in Git does not mean the PR is current.
- Separate facts you checked from your judgment.
- Post PR comments only when asked, through
ds-pr-comments.
