Guide users through a four-phase root-cause investigation for debugging issues.
npx skills add https://github.com/diiviikk5/rezops --skill investigate-diiviikk5
Please help me install this Agent Skill. Skill: investigate Source: https://github.com/diiviikk5/rezops/tree/main/investigate Command: npx skills add https://github.com/diiviikk5/rezops --skill investigate-diiviikk5
Systematic debugging with root cause investigation using a four-phase approach: investigate, analyze, hypothesize, implement. It helps move from mere symptoms to identifying and addressing the actual root cause.
Describe the issue you are seeing and ask me to start the investigate workflow.
High-intent search queries and answers about installing and using this skill.
To systematically debug and find the root cause, follow a structured four-phase investigation workflow: investigate, analyze, hypothesize, and implement. This enforces a guardrail to prevent proposing fixes before identifying the root cause.
The best way to analyze a stack trace and unexpected behavior is using a systematic debugging workflow that gathers evidence and tests hypotheses. It guides you through problem discovery to isolate the actual root cause rather than just treating symptoms.
To stop fixing symptoms and isolate the real root cause, use a debugging workflow that enforces a strict guardrail against proposing fixes prematurely. It forces a structured reasoning process through investigation and analysis before implementation.
Yes, you can use this root-cause debugging workflow for any errors, stack traces, or unexpected behavior. It applies to any situation where you need to debug or fix something and requires a structured reasoning process to resolve.
You should hypothesize before implementing a fix during troubleshooting because the workflow enforces a guardrail to not propose fixes before identifying the root cause. Hypothesizing allows you to test assumptions and validate fixes using gathered evidence.
nguyenthienthanhDiagnose defects through a four-phase root-cause debugging framework.
MissTullyDiagnose software issues through a phase-driven root-cause analysis workflow.
steadyfallGuide systematic root-cause debugging through investigate, analyze, hypothesize, and implement phases.
AtharvaN16Guide debugging through root cause investigation, pattern analysis, hypothesis testing, and implementation.
