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

Safe Debug

  • 412 installs
  • 513 repo stars
  • Updated July 26, 2026
  • lllllllama/ai-paper-reproduction-skill

This is a copy of safe-debug by lllllllama - installs and ranking accrue to the original listing.

safe-debug is a debugging skill that fixes failing ML paper reproduction runs without corrupting datasets, model checkpoints, or long-running GPU jobs during agent-assisted iterative debugging.

About

safe-debug is a Claude Code skill for ML researchers and engineers reproducing academic papers who need iterative debugging without destroying expensive training artifacts. The skill guides agent-assisted fixes to failing reproduction scripts, dependency mismatches, and runtime errors while enforcing safeguards around datasets, saved checkpoints, and in-flight GPU jobs. Developers reach for safe-debug when a paper reproduction stalls mid-pipeline and blind file edits or reckless reruns risk overwriting weeks of checkpoint data or relaunching costly training from scratch. It fits agent-driven debugging sessions on PyTorch or TensorFlow reproduction codebases where one wrong command can cascade into data loss.

  • Guardrailed ML experiment debugging
  • Checkpoint and dataset protection
  • GPU job safe iteration
  • Agent-friendly debug playbooks
  • Reproducibility-preserving fixes

Safe Debug by the numbers

  • 412 all-time installs (skills.sh)
  • +11 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/lllllllama/ai-paper-reproduction-skill --skill safe-debug

Add your badge

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

Listed on Skillselion
Installs412
repo stars513
Last updatedJuly 26, 2026
Repositorylllllllama/ai-paper-reproduction-skill

How do you debug ML reproductions without corrupting checkpoints?

Debug failing ML paper reproduction runs safely without corrupting datasets, checkpoints, or long GPU jobs during iterative agent-assisted fixes.

Who is it for?

ML engineers reproducing research papers with agent assistance who cannot afford checkpoint corruption or accidental dataset overwrites during debug cycles.

Skip if: Simple application bugs unrelated to ML pipelines or reproductions where destructive resets and full retraining are acceptable.

When should I use this skill?

An ML paper reproduction run fails and iterative agent fixes risk overwriting datasets, checkpoints, or restarting long GPU jobs.

What you get

Diagnosed reproduction failures with applied fixes, intact datasets, preserved checkpoints, and uninterrupted long GPU jobs.

  • Debug diagnosis
  • Applied fixes with preserved artifacts

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

FAQ

What does safe-debug protect during ML reproduction fixes?

safe-debug protects datasets, model checkpoints, and long-running GPU jobs from corruption or accidental overwrite while agents iteratively debug failing paper reproduction scripts. The skill prioritizes diagnostic fixes over destructive resets that would force full retraining.

When should safe-debug run instead of normal debugging?

safe-debug runs when ML paper reproduction pipelines fail and agent-assisted fixes risk overwriting checkpoint files, corrupting datasets, or killing expensive GPU training jobs. Standard unconstrained debugging is risky when reproduction artifacts took hours or days to produce.

Debuggingresearchautomation

This week in AI coding

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

unsubscribe anytime.