{"enrichment":{"faq":[{"a":"Debugging Protocol is a disciplined four-phase investigation process that enforces root cause analysis before any code change. It prevents jumping to fixes without understanding why problems exist, using the Iron Law (investigate first) and Three Strikes Rule (escalate after three failed attempts) to guide systematic problem-solving across your team.","q":"What is a debugging protocol?"},{"a":"Debugging Protocol teaches a repeatable methodology with four distinct phases: first, isolate and reproduce the problem consistently; second, gather evidence through logs and system state; third, form and test hypotheses about root causes; fourth, implement and verify the fix. This sequence ensures you understand the problem before changing code.","q":"How do I debug code using this structured approach?"},{"a":"Debugging Protocol emphasizes the Iron Law\u2014investigate first, act second\u2014and the Three Strikes Rule, which escalates issues after three failed attempts. These principles prevent wasted effort on guesses and keep teams focused on evidence-based diagnosis rather than trial-and-error fixes.","q":"What are the best practices for systematic debugging?"},{"a":"Debugging Protocol provides a framework to standardize your team's problem-solving approach. By adopting its four-phase process and core rules (Iron Law and Three Strikes), you create a repeatable protocol that all team members follow, reducing inconsistency and improving time-to-resolution across debugging efforts.","q":"How can I establish a debugging protocol for my team?"},{"a":"Debugging Protocol improves efficiency by eliminating guesswork through its structured phases and escalation rules. The Three Strikes Rule prevents endless failed attempts, while the Iron Law ensures investigation happens upfront. This systematic approach reduces wasted effort and accelerates root cause discovery.","q":"How do I debug efficiently and reduce resolution time?"},{"a":"Debugging Protocol covers systematic problem diagnosis through evidence gathering, hypothesis formation, and methodical testing. Its techniques include isolating reproduction steps, analyzing logs and system state, forming testable theories about root causes, and verifying fixes. The framework applies across code and application debugging scenarios.","q":"What debugging techniques and strategies does this protocol teach?"}],"shadow_tags":["systematic-approach","troubleshooting-framework","error-diagnosis","workflow-optimization","developer-methodology"],"summary_rewrite":"Debugging Protocol teaches a disciplined four-phase investigation process that enforces root cause analysis before any code change. It prevents the common trap of jumping to fixes without understanding why problems exist, using the Iron Law (investigate first) and Three Strikes Rule (escalate after three failed attempts) to guide systematic problem-solving."},"gist":{"api_url":"https://skillfed.io/api/skills/jwilger/agent-skills/debugging-protocol.json","as_of":"2026-07-05","description":"Debugging Protocol provides a structured 4-phase method to investigate and fix code failures by understanding.","install":{"manual":["git clone https://github.com/jwilger/agent-skills","cp -r agent-skills ~/.claude/skills/debugging-protocol"],"primary":"npx skillfed install jwilger/agent-skills/debugging-protocol","version":"d2fe3cf8"},"kind":"skill","mirror_url":"https://skillfed.io/jwilger/agent-skills/debugging-protocol.md","similar":[{"id":"catlog22/Claude-Code-Workflow/investigate","name":"investigate","publisher":"catlog22/Claude-Code-Workflow","url":"https://skillfed.io/catlog22/Claude-Code-Workflow/investigate"},{"id":"softspark/ai-toolkit/debug","name":"debug","publisher":"softspark/ai-toolkit","url":"https://skillfed.io/softspark/ai-toolkit/debug"},{"id":"FradSer/dotclaude/systematic-debugging","name":"systematic-debugging","publisher":"FradSer/dotclaude","url":"https://skillfed.io/FradSer/dotclaude/systematic-debugging"},{"id":"jwilger/agent-skills/ci-integration","name":"Ci Integration","publisher":"jwilger/agent-skills","url":"https://skillfed.io/jwilger/agent-skills/ci-integration"},{"id":"NousResearch/hermes-agent/systematic-debugging","name":"systematic-debugging","publisher":"NousResearch/hermes-agent","url":"https://skillfed.io/NousResearch/hermes-agent/systematic-debugging"}],"title":"Debugging Protocol by jwilger: Learn a structured approach \u2014 SkillFed","use":{"when":["Debugging Protocol teaches a repeatable methodology with four distinct phases: first, isolate and reproduce the problem consistently.","Debugging Protocol emphasizes the Iron Law\u2014investigate first, act second\u2014and the Three Strikes Rule."]},"what":{"lead":"Debugging Protocol provides a structured 4-phase method to investigate and fix code failures by understanding root causes before attempting solutions.","rest":"Debugging Protocol teaches a disciplined four-phase investigation process that enforces root cause analysis before any code change. It prevents the common trap of jumping to fixes without understanding why problems exist, using the Iron Law (investigate first) and Three Strikes Rule (escalate after three failed attempts) to guide systematic problem-solving."}},"id":"jwilger/agent-skills/debugging-protocol","install":{"mode":"external","repo":"https://github.com/jwilger/agent-skills"},"links":{"html":"https://skillfed.io/jwilger/agent-skills/debugging-protocol","md":"https://skillfed.io/jwilger/agent-skills/debugging-protocol.md","repo":"https://github.com/jwilger/agent-skills"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":0,"language":"Shell","last_updated":"2026-07-05","license":"CC0-1.0","name":"Debugging Protocol","publisher":"jwilger","stars":1},"relations":{"categories":["software-development","quality-assurance"],"similar":[{"id":"catlog22/Claude-Code-Workflow/investigate"},{"id":"nyldn/claude-octopus/skill-debug"},{"id":"softspark/ai-toolkit/debug"},{"id":"FradSer/dotclaude/systematic-debugging"},{"id":"jwilger/agent-skills/ci-integration"},{"id":"NousResearch/hermes-agent/systematic-debugging"},{"id":"MageByte-Zero/spec-superflow/bug-investigator"},{"id":"jwilger/agent-skills/memory-protocol"},{"id":"mateaix/mateclaw/systematic-debugging"},{"id":"moltis-org/moltis/systematic-debugging"}]},"slug":{"owner":"jwilger","repo":"agent-skills","skill":"debugging-protocol"},"version":"d2fe3cf8"}