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

Safe Debug

  • 29 installs
  • 512 repo stars
  • Updated July 26, 2026
  • lllllllama/ai-paper-reproduction-skills

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

Helps with debugging tasks during AI-assisted development.

About

safe-debug is a Claude Code skill for debugging. It helps solo builders move faster with AI-assisted coding.

  • safe-debug
  • Debugging
  • AI-coding skill

Safe Debug by the numbers

  • 29 all-time installs (skills.sh)
  • Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/lllllllama/ai-paper-reproduction-skills --skill safe-debug

Add your badge

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

Listed on Skillselion
Installs29
repo stars512
Last updatedJuly 26, 2026
Repositorylllllllama/ai-paper-reproduction-skills

What it does

Helps with debugging tasks during AI-assisted development.

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

Debuggingtesting

This week in AI coding

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

unsubscribe anytime.