phase-gated-debugging
/phase-gated-debugging
Use when debugging any bug. Enforces a 5-phase protocol where code edits are blocked until root cause is confirmed. Prevents premature fix attempts.
- Author
- FrancoStino ↗
- Repository
- opencode-skills-collection ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when debugging any bug. Enforces a 5-phase protocol where code edits are blocked until root cause is confirmed. Prevents premature fix attempts.
Original author description
Use when debugging any bug. Enforces a 5-phase protocol where code edits are blocked until root cause is confirmed. Prevents premature fix attempts.
How it works
- Overview
- When to Use
- The Protocol
- Bug-Type Strategies
- Key Rules
- Example
- Limitations
SKILL.md preview
--- name: phase-gated-debugging description: "Use when debugging any bug. Enforces a 5-phase protocol where code edits are blocked until root cause is confirmed. Prevents premature fix attempts." risk: safe source: community date_added: "2026-03-28" --- # Phase-Gated Debugging ## Overview AI coding agents see an error and immediately edit code. They guess at fixes, get it wrong, and spiral. This skill enforces a strict 5-phase protocol where you CANNOT edit source code until the root cause is identified and confirmed. Based on [claude-debug](https://github.com/krabat-l/claude-debug) (full plugin with PreToolUse hook enforcement). ## When to Use Use this skill when: - a bug keeps getting "fixed" without resolving the underlying issue - you need to slow an agent down and force disciplined debugging before code edits - the failure is intermittent, a regression, performance-related, or otherwise hard to isolate - you want an explicit user confirmation checkpoint before any fix is applied ## The Protocol ### Phase 1: REPRODUCE Run the failing command/test. Capture the exact error. Run 2-3 times for consistency. - Do NOT read source code - Do NOT hypothesize - Do NOT edit any files ### Phase 2: ISOLATE Read code. Add diagnostic logging marked `// DEBUG`. Re-run with diagnostics. Binary search to narrow down. - Only `// DEBUG` marked logging is allowed - Do NOT fix the bug even if you see it ### Phase 3: ROOT CAUSE Analyze WHY at the isolated location. Use "5 Whys" technique. Remove debug logging. State: "This is my root cause analysis: [explanation]. Do you agree, or should I investigate further?" **WAIT for user confirmation. Do NOT proceed without it.** ### Phase 4: FIX Remove all `// DEBUG` lines. Apply minimal change addressing confirmed root cause. - Only edit files related to root cause - Do NOT refactor unrelated code ### Phase 5: VERIFY Run original failing test — must pass. Run related tests. For intermittent bugs, run 5+ times. If verification fails: root cause was wrong, go back to Phase 2. ## Bug-Type Strategies | Type | Technique | |------|-----------| | Crash/Panic | Stack trace backward — trace the bad value to its source | | Wrong Output | Binary search — log midpoint, halve search space each iteration | | Intermittent | Compare passing vs failing run logs — find ordering divergence | | Regression | `git bisect` — find the offending commit | | Performance | Timing at stage boundaries — find the bottleneck | ## Key Rules 1. NEVER edit source code in phases 1-3 (except `// DEBUG` in phase 2) 2. NEVER proceed past phase 3 without user confirmation 3. ALWAYS reproduce before investigating 4. ALWAYS verify after fixing ## Example **User request:** > a bug keeps getting "fixed" without resolving the underlying issue; diagnose it and return the concrete next action. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · FrancoStino/opencode-skills-collection | 100 | MIT |
| sickn33/agentic-awesome-skills | 100 | MIT |
| LiHongwei-cn/lihongwei-cn | 90 | MIT |
Database snapshot: 13.11.2026 · package version d83ce9eed441 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100codex-systematic-debugging
Use for bugs, test failures, broken behavior, or unexpected results; enforces 4-phase root-cause debugging before fixes. - 100code-showcase-systematic-debugging
Four-phase debugging methodology with root cause analysis. Use when investigating bugs, fixing test failures, or troubleshooting unexpected behavior. Emphasizes NO FIXES WITHOUT ROOT CAUSE FIRST. - 100code-showcase-systematic-debugging
Four-phase debugging methodology with root cause analysis. Use when investigating bugs, fixing test failures, or troubleshooting unexpected behavior. Emphasizes NO FIXES WITHOUT ROOT CAUSE FIRST. - 100systematic-debugging
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions. Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. - 100systematic-debugging
4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues. - 100debugging
Systematic 4-phase debugging with root cause investigation. Use when fixing bugs to prevent random fixes.