safe-debug
Compétence de débogage rigoureux / audit rigoureux pour les travaux de recherche en deep learning. À utiliser lorsque l'utilisateur colle un traceback, une erreur de terminal, une OOM CUDA, un échec de chargement de checkpoint, une incompatibilité de forme, un symptôme de perte NaN ou un échec d'entraînement et souhaite un diagnostic conservateur avant toute correction, avec des correctifs de débogage clairement séparés des contributions de recherche. Ne pas utiliser pour un refactoring large, une adaptation spéculative, un patching exploratoire automatique ou une familiarisation générale avec le dépôt.
npx skills add https://github.com/lllllllama/rigorpilot-skills --skill safe-debugsafe-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.