run-tests
Run tests with debug logging. Use when user says 'test', 'テスト', or asks to verify changes.
Works with
--- name: run-tests description: Run tests with debug logging. Use when user says 'test', 'テスト', or asks to verify changes. license: MIT --- 変更を検証するため、テストをデバッグ出力付きで実行する。 ```bash # 指定ファイル LOG_LEVEL=debug deno test $ARGUMENTS --allow-env --allow-write --allow-read # 全テスト（引数なし時） LOG_LEVEL=debug deno test --allow-env --allow-write --allow-read # 全CI（推奨） deno task ci ``` ## テスト構造 ### 単体テスト（lib/ 配下、実装と同一ディレクトリ） `lib/factory/*.test.ts`, `lib/types/*_test.ts` など ### 統合・E2Eテスト（tests/ 配下、番号付きドメイン構造） | Dir | Content | |-----|---------| | `tests/0_core_domain/` | 核心ドメイン統合テスト（プロンプトパス解決等） | | `tests/4_cross_domain/` | ドメイン間統合・E2Eテスト | | `tests/integration/` | JSR統合・設定プロファイルテスト | | `tests/fixtures/` | テストフィクスチャ | ### 実行順序（CLAUDE.md 規約） 1. `deno task ci` で全体把握 2. `DEBUG=true deno task ci` で詳細確認 3. 個別テストファイルで特定エラー調査
More Debugging skills
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
explore-code
lllllllama/rigorpilot-skills
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline reproduction, conservative debugging, environment setup, verified contribution claims, or default repository analysis.
safe-debug
lllllllama/rigorpilot-skills
Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.
