safe-debug
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.
适合你，如果需要安全调试深度学习代码且不影响研究贡献
npx oh-my-skill add lllllllama/rigorpilot-skills/safe-debugcurl -fsSL https://oh-my-skill.com/install.sh | bash -s -- lllllllama/rigorpilot-skills/safe-debugnpx oh-my-skill verify lllllllama/rigorpilot-skills/safe-debug怎么用
商店整理自技能原文 · 版本 3ab5052 · 表述以原文为准当您粘贴深度学习训练或推理中的具体错误（如报错信息、显存溢出、检查点加载失败、形状不匹配、NaN损失等）时，Claude 会先诊断根因，然后保守地提出最小修复方案，但不会自动修改代码，而是请求您确认。最终输出诊断报告、补丁计划及状态文件。
当您粘贴终端错误、训练失败症状（如形状不匹配、NaN损失）并希望进行保守诊断时触发。
技能原文 SKILL.md
safe-debug
Use this as the Rigor Debug / Rigor Audit skill. The installed slug remains safe-debug for compatibility.
Use the shared operating principles in ../../references/agent-operating-principles.md; this skill should guide conservative diagnosis without blocking the model from finding the local root cause.
When to apply
- The user provides a traceback, terminal error, or concrete training or inference failure symptom.
- The user wants diagnosis, root-cause narrowing, and minimal patch suggestions before code is changed.
- The user wants a safe debug flow with explicit human approval before mutation.
When not to apply
- When the user wants a broad repository walkthrough without an active failure.
- When the task is speculative experimentation or code adaptation.
- When the user is asking for a large refactor or readability rewrite.
Clear boundaries
- Diagnose first.
- Do not modify repository code by default.
- If a patch is needed, propose the smallest fix and require explicit approval first.
- Escalate savepoint or branch creation before medium-risk or high-risk changes.
- A debug fix is not automatically a research contribution; if it changes experiment meaning or comparability, say so explicitly.
Output expectations
debug_outputs/DIAGNOSIS.mddebug_outputs/PATCH_PLAN.mddebug_outputs/status.json
Notes
Use references/debug-policy.md, ../../references/research-rigor-principles.md, and the shared ../../references/research-pitfall-checklist.md.