사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/aicodeking/deepseek-stack --skill ds-unstick시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
ds-unstick
When two fixes fail the same way, the problem is usually a wrong belief, not a wrong edit. Find that belief and test it.
Steps
- Stop editing. Do not try a third variation of the same fix.
- Write down each failed attempt in one line: what you changed and what happened. Include the exact error text.
- Write the assumption that all of those attempts shared. Typical examples: "this file is the one that runs", "the config is loaded", "the function receives a string", "the cache is cleared", "the error comes from my code". Name one, in one sentence.
- Test that assumption directly with the cheapest probe that gives a yes or no answer: a print statement, a log line, a
whichor--version, a grep for the real call site, a minimal script, or a read of the docs for the exact version installed. Paste the result. - If the assumption is false, you have found the real problem. Plan the fix from the new fact.
- If the assumption holds, list 3 different approaches. "Different" means another mechanism, library, layer or data path, not a tweak of the same edit. Give each approach one line on cost and risk.
- Pick one approach and say why in one sentence.
- Restart from a clean state if the failed attempts left debris: revert them with git (
git stashorgit checkout -- <files>), then apply only the chosen approach. - Record the false assumption or the chosen approach in PROGRESS.md (see ds-context-reset) so a later session does not repeat the attempts.
- Return to ds-verify-loop with the new approach.
Stop when
- The probe in step 4 explains the failure, or the new approach passes its check.
- Two rounds of this skill have failed. Stop and report to the user: the attempts, the assumptions you tested, and the evidence. Ask for direction.
Rules
- Do not repeat a fix that has already failed, even with small changes.
- Evidence beats reasoning. If a probe takes a minute, run it.
- Keep the failed-attempt list, because it is the most useful part of the report.
- Use a clean state before a new approach, so that old edits cannot hide the result.
