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.
Install
With your agent
Install OMGSkills skill "lllllllama/rigorpilot-skills:safe-debug" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/lllllllama/RigorPilot-Skills /tmp/RigorPilot-Skills && ln -s /tmp/RigorPilot-Skills/skills/safe-debug ~/.claude/skills/safe-debug
From README
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 ../ai-research-reproduction/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.
