사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/aicodeking/deepseek-stack --skill ds-tdd시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
ds-tdd
Make the bug executable before touching production code, so the fix is proven, not claimed.
Steps
- Pin down the bug: expected behavior, actual behavior, the code path, and the smallest way to reproduce it.
- Find the nearest existing test style for that code path. Use it. Do not build a new harness just for this.
- Write the smallest test that would have caught the bug. It checks intended behavior, not the current implementation.
- Run it. Show the output. It must fail, and fail for the bug, not for a typo or missing import. If not, fix the test first.
- Make the smallest production change that gives the intended behavior without breaking nearby contracts.
- Run the new test and the surrounding suite. Show the output.
- If a clean test is impractical (heavy setup, brittle mocks, production-only state), use the closest runnable check instead: a script, a repro command or a log check. Say why you skipped the test.
Stop when
- The new test failed before the fix and passes after it, both shown with output, and the surrounding suite passes.
- Or after three fix attempts the test still fails. Stop, report what you learned and run /ds-unstick.
Rules
- Never edit a test to match a wrong implementation.
- Do not weaken existing assertions without a clear, stated reason.
- No test beats a bad test: one that mostly tests mocks, depends on timing, or would be deleted right after.
