Identify and fix root causes of bugs through a four-phase workflow.
npx skills add https://github.com/ekrishgupta/gemstack --skill investigate-ekrishgupta
Please help me install this Agent Skill. Skill: investigate Source: https://github.com/ekrishgupta/gemstack/tree/main/investigate Command: npx skills add https://github.com/ekrishgupta/gemstack --skill investigate-ekrishgupta
Systematic debugging with a focus on root cause analysis across investigation, analysis, hypothesis testing, implementation, and verification.
Describe the issue you're facing and ask /investigate to start root-cause analysis.
High-intent search queries and answers about installing and using this skill.
To find the root cause of a software bug, use a structured four-phase workflow: investigate, analyze, hypothesize, and implement. This approach relies on proactive data gathering and evidence-based hypothesis testing to reduce guesswork across code, tests, and environments.
Systematic root-cause debugging involves collecting symptoms, inspecting code, reproducing issues, proposing fixes, and verifying results. Using shell utilities like Grep, Read, Write, Edit, and Bash ensures evidence-based analysis rather than trial and error.
To reproduce a runtime error and verify a fix, gather initial symptoms, inspect relevant code with Grep and Read, and use Bash to reproduce the issue. After implementing a fix with Edit, verify the results to ensure the root cause is resolved.
Yes, systematic code investigation requires tools like Grep, Read, Write, Edit, and Bash. These shell utilities collect symptoms, inspect code, reproduce issues, apply fixes, and verify results throughout the debugging workflow.
Structured hypothesis testing reduces rework by enforcing evidence-based analysis during debugging. By proactively gathering data and testing hypotheses before implementing changes, you minimize guesswork and target the actual root cause directly.
Documenting root cause analysis during troubleshooting improves long-term code health and team learning. Structured debugging provides guidance for collaboration, ensuring that evidence, hypotheses, and verification steps are recorded for future reference.
Andy-HNUGuide structured root-cause investigation across symptoms, code paths, and changes.
BradliebsDiagnose software failures through a four-phase root-cause investigation workflow.
ibalasiteDiagnose software bugs and runtime errors with root cause analysis and regression tests.
chriswesttMonitor deployed apps for console errors, performance regressions, and page failures.
