메뉴
Start bug work by proving the reported bug with a failing regression test before attempting a fix. Use when the user reports a bug, asks to fix a bug, or describes a regression, failing behavior, or reproduction case with a plausible test surface.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/vana-com/vana-sdk --skill bug-repro-test-first명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | bug-repro-test-first |
| description | Start bug work by proving the reported bug with a failing regression test before attempting a fix. Use when the user reports a bug, asks to fix a bug, or describes a regression, failing behavior, or reproduction case with a plausible test surface. |
Use this when the user reports a bug or asks for a bug fix.
Read references/tangming2005-test-first-bug-report.md if you need the source note behind this workflow.
Do not start by fixing the code.
First write or adapt a test that fails for the reported bug. The test is the definition of the bug.
If there is no useful test surface, create the narrowest reproducible check available instead (a script under scripts/, a curl against a local server, an e2e case), then state why a regression test was not practical before fixing production code.
Reproduce or inspect the failure enough to choose the narrowest useful test. Tests are co-located *.test.ts in packages/vana-sdk/src and use Vitest with mocked viem clients and fetch.
Add a failing test that captures the bug, preferably near existing coverage for the same behavior. Assert on the public contract (route status and body shape, exported function result, error code or class), not on log text or private helpers.
Run that test and confirm it fails for the expected reason:
cd packages/vana-sdk && npx vitest run src/<file>.test.ts
No build is needed for unit tests; turbo builds workspace dependencies first when you go through the root npm test.
Only then change production code.
Run the same test and confirm it passes.
Run the smallest relevant surrounding test/check slice, then the repo proof before handoff:
npm run typecheck && npm run lint && npm test
If the user explicitly asks for subagents or the active tool policy permits delegation for this task, spawn fix workers only after the failing test exists. Give each worker the failing test command and a disjoint write scope.
If delegation is not available or not appropriate, fix locally after proving the failing test.