Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
lllllllama avatar

Safe Debug

  • 176k installs
  • 512 repo stars
  • Updated July 26, 2026
  • lllllllama/rigorpilot-skills

safe-debug is a Claude Code skill for conservative diagnosis and minimal patching of deep learning errors with explicit human approval.

About

A debugging skill for deep learning research. Use it when you have a traceback, training failure, or error symptom and want conservative diagnosis before any code changes.

  • Conservative diagnosis of tracebacks, CUDA OOM, and shape mismatches
  • Proposes minimal fixes with explicit human approval before patching
  • Separates debug fixes from research contributions clearly

Safe Debug by the numbers

  • 175,924 all-time installs (skills.sh)
  • +25,325 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #6 of 610 Debugging skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

safe-debug capabilities & compatibility

Capabilities
error diagnosis · root cause narrowing · patch planning · evidence collection
Use cases
debugging · code review · research
npx skills add https://github.com/lllllllama/rigorpilot-skills --skill safe-debug

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs176k
repo stars512
Security audit3 / 3 scanners passed
Last updatedJuly 26, 2026
Repositorylllllllama/rigorpilot-skills

What it does

Diagnose deep learning training and inference errors with minimal patch suggestions.

Who is it for?

Diagnosing tracebacks,CUDA OOM analysis,NaN loss investigation,Training failure diagnosis

Skip if: Broad refactoring,Speculative adaptation,Automatic exploratory patching,General repository familiarization

When should I use this skill?

The user provides a traceback, terminal error, or concrete training/inference failure symptom and wants diagnosis with minimal patch suggestions.

What you get

DIAGNOSIS.md identifying root cause, PATCH_PLAN.md with minimal suggested fixes, and status.json documenting the issue.

  • debug_outputs/DIAGNOSIS.md
  • debug_outputs/PATCH_PLAN.md
  • debug_outputs/status.json

By the numbers

  • 3 structured debug output files: DIAGNOSIS.md, PATCH_PLAN.md, status.json

Files

SKILL.mdMarkdownGitHub ↗

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.md
  • debug_outputs/PATCH_PLAN.md
  • debug_outputs/status.json

Notes

Use references/debug-policy.md, ../../references/research-rigor-principles.md, and the shared references/research-pitfall-checklist.md.

Related skills

Forks & variants (3)

Safe Debug has 3 known copies in the catalog totaling 440 installs. They canonicalize to this original listing.

How it compares

Use safe-debug for read-only failure triage; use explore-code only after explicit authorization to apply exploratory fixes on an isolated branch.

FAQ

Does this modify code automatically?

No. Diagnosis is first; if a patch is needed, it's proposed and requires explicit approval.

Is a debug fix a research contribution?

Not automatically. If it changes experiment meaning or comparability, that's stated explicitly.

Is Safe Debug safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Debuggingbackenddevops

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.