Guide root-cause debugging through investigate, analyze, hypothesize, and implement phases.
npx skills add https://github.com/MissTully/Gstack --skill investigate-misstully
Please help me install this Agent Skill. Skill: investigate Source: https://github.com/MissTully/Gstack/tree/main/investigate Command: npx skills add https://github.com/MissTully/Gstack --skill investigate-misstully
Root-cause debugging is a structured, repeatable approach that helps engineers quickly find the true cause of bugs and avoid premature fixes.
Describe the issue you want investigated and I will guide you through the four-phase root-cause workflow.
High-intent search queries and answers about installing and using this skill.
Root-cause debugging is a structured approach that isolates the true cause of software bugs before applying fixes. It prevents premature patches by guiding engineers through systematic investigation, ensuring the underlying issue is resolved rather than just symptoms.
Debug a regression systematically by following a four-phase workflow: investigate, analyze, hypothesize, and implement. Reproduce the error, reason about the isolated root cause, and validate the fix before deployment.
Yes. The workflow uses deterministic Bash, Grep, Glob, Read, and Write tools to reproduce errors, search codebases, and validate fixes. It also supports WebSearch and AskUserQuestion for gathering external context.
Debug performance problems across integrations by following a disciplined four-phase process: investigate symptoms, analyze data, hypothesize the root cause, and implement a verified fix using deterministic tooling.
Yes. The workflow applies to errors, exceptions, and performance problems across any codebases, services, or integrations. It uses generic file and shell tools rather than language-specific analyzers.
Avoid a structured root-cause investigation for trivial syntax errors or immediate hotfixes where the cause is already obvious, as the four-phase process adds overhead best reserved for complex regressions.
sQVeDiagnose bugs by tracing evidence and generating a BR issue template.
baleen37Debug software through a four-phase root cause investigation framework.
zhifengzhang-szGuide structured four-phase debugging to identify root causes of software issues.
CaptainCrouton89Automate software tests to verify functionality against acceptance criteria.
