Debug software issues through a four-phase root-cause investigation workflow.
npx skills add https://github.com/nyldn/claude-octopus --skill skill-debug-nyldn
Please help me install this Agent Skill. Skill: skill-debug Source: https://github.com/nyldn/claude-octopus/tree/main/skills/skill-debug Command: npx skills add https://github.com/nyldn/claude-octopus --skill skill-debug-nyldn
Systematic debugging workflow to prevent patch-based firefighting by enforcing root-cause investigation before fixes.
Initiate Phase 1: root cause investigation to reproduce the bug, gather evidence, and trace data flow.
High-intent search queries and answers about installing and using this skill.
A systematic root-cause debugging workflow enforces evidence gathering, pattern analysis, and hypothesis testing before implementing fixes. It prevents patch-based firefighting by requiring a structured four-phase process to identify and resolve bugs across software engineering projects.
To fix production bugs without firefighting, reproduce the issue consistently, gather evidence across components, and form a single hypothesis. You then create a failing test, implement a single fix, and verify the resolution with guardrails to ensure the root cause is resolved.
Yes, you can use this debugging workflow for performance problems, integration issues, test failures, and production bugs. It applies a structured pattern analysis and hypothesis testing approach to identify root causes across diverse software engineering scenarios.
The best way to verify a bug fix is to require a failing test before implementing the code change. After the single fix is applied, run verification tests and guardrails to validate the resolution and confirm the root cause is eliminated without regressions.
You should stop debugging and reconsider your architecture when red flags or guardrails indicate fundamental architecture issues. The workflow halts the debugging process if pattern analysis or hypothesis testing reveals systemic problems rather than isolated bugs.
derHakenTrace data flow and apply a four-phase process to fix root causes.
ultramaxoAIEnforce red-green-refactor cycles requiring failing tests before production code.
Donaldshen27Identify bug root causes through a four-phase systematic debugging framework.
hafiznaveedchuhan-ctrlGuide software bug investigations through structured phases from data collection to fix implementation.
