safe-debug
installsforks
How to install safe-debug?
lllllllama/rigorpilot-skills/safe-debug
$npx -y skills add lllllllama/RigorPilot-Skills --skill safe-debugRigor 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 c
SKILL.md
| 1 | # safe-debug |
| 2 | |
| 3 | Use this as the Rigor Debug / Rigor Audit skill. The installed slug remains |
| 4 | `safe-debug` for compatibility. |
| 5 | |
| 6 | Use the shared operating principles in |
| 7 | `../../references/agent-operating-principles.md`; this skill should guide |
| 8 | conservative diagnosis without blocking the model from finding the local root |
| 9 | cause. |
| 10 | |
| 11 | ## When to apply |
| 12 | |
| 13 | - The user provides a traceback, terminal error, or concrete training or inference failure symptom. |
| 14 | - The user wants diagnosis, root-cause narrowing, and minimal patch suggestions before code is changed. |
| 15 | - The user wants a safe debug flow with explicit human approval before mutation. |
| 16 | |
| 17 | ## When not to apply |
| 18 | |
| 19 | - When the user wants a broad repository walkthrough without an active failure. |
| 20 | - When the task is speculative experimentation or code adaptation. |
| 21 | - When the user is asking for a large refactor or readability rewrite. |
| 22 | |
| 23 | ## Clear boundaries |
| 24 | |
| 25 | - Diagnose first. |
| 26 | - Do not modify repository code by default. |
| 27 | - If a patch is needed, propose the smallest fix and require explicit approval first. |
| 28 | - Escalate savepoint or branch creation before medium-risk or high-risk changes. |
| 29 | - A debug fix is not automatically a research contribution; if it changes |
| 30 | experiment meaning or comparability, say so explicitly. |
| 31 | |
| 32 | ## Output expectations |
| 33 | |
| 34 | - `debug_outputs/DIAGNOSIS.md` |
| 35 | - `debug_outputs/PATCH_PLAN.md` |
| 36 | - `debug_outputs/status.json` |
| 37 | |
| 38 | ## Notes |
| 39 | |
| 40 | Use `references/debug-policy.md`, `../../references/research-rigor-principles.md`, and the shared `references/research-pitfall-checklist.md`. |
People who liked this also viewed
6 picksType
- azure-diagnosticsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deploySkillsJul 2026
- systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesSkillsJul 2026
- explore-runRigor Improve / Rigor Explore run leaf skill for bounded exploratory evidence in deep learning research repositories. Use when the researcher explicitly authorizes exploratory runs such as small-subseSkillsMay 2026
- minimal-run-and-auditRigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation SkillsMay 2026
- insforge-debugUse when diagnosing problems in an InsForge project — reactive failures (SDK error object, HTTP 4xx/5xx, gateway timeout 502/503/504, edge function failure or timeout, login/OAuth/auth errors, RLS denSkillsJul 2026
- fix-errorsFix compilation errors, linting issues, and test failures in the warp Rust codebase. Covers presubmit checks, WASM-specific errors, and running specific tests. Use when the user hits build errors, cliSkillsJul 2026
