debug
Full debugging workflow — reproduce the bug with a failing test, perform root cause analysis, then implement a minimal fix.
Works with
--- name: debug description: Full debugging workflow — reproduce the bug with a failing test, perform root cause analysis, then implement a minimal fix. license: Apache-2.0 --- # Debug Debug a reported issue using a structured reproduction-then-fix approach. ## Phase 1: Reproduction & Root Cause Analysis 1. **Investigate** — Analyze the bug report for key symptoms and error messages 2. **Trace** — Search the codebase for error occurrence patterns, trace from symptom to source 3. **Root cause** — Identify the root cause through data flow analysis and edge case checking 4. **Reproduce** — Create a minimal failing test case that reproduces the exact error 5. **Document** — Clearly document the root cause and reproduction steps ## Phase 2: Fix Implementation 1. **Plan** — Analyze the optimal fix approach based on root cause, check for similar fixes in the codebase 2. **Implement** — Make the minimal, targeted fix that addresses the root cause 3. **Verify** — Run the failing test to confirm it passes, then run the full test suite to check for regressions ## Principles - **Minimal changes** — Fix the bug, nothing more - **Targeted** — Only touch affected code paths - **Tested** — The fix must make the failing test pass and not break existing tests - **No unrelated improvements** — Stay focused on the specific bug
More Debugging skills
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
explore-code
lllllllama/rigorpilot-skills
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline reproduction, conservative debugging, environment setup, verified contribution claims, or default repository analysis.
safe-debug
lllllllama/rigorpilot-skills
Rigor 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 clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.
