Enforce root-cause investigation before applying software fixes.
npx skills add https://github.com/lyh2/gstack-deepseek --skill investigate-lyh2
Please help me install this Agent Skill. Skill: investigate Source: https://github.com/lyh2/gstack-deepseek/tree/main/investigate Command: npx skills add https://github.com/lyh2/gstack-deepseek --skill investigate-lyh2
Systematic debugging with a structured root-cause investigation workflow to prevent patchwork fixes and recurring outages.
Describe a bug you see, then run the root-cause investigation workflow to identify the underlying cause.
High-intent search queries and answers about installing and using this skill.
To find the root cause of a bug regression, you need a systematic debugging workflow that enforces evidence gathering and structured analysis before implementing fixes. This approach guides you from symptoms to evidence-driven remedies across four phases: investigate, analyze, hypothesize, and implement.
The best way to debug complex codebases for performance issues is using a structured root-cause investigation approach. It enforces tool-assisted analysis and safety checks to prevent unsafe changes, guiding you systematically from observed symptoms to evidence-driven remedies.
To start a systematic investigation workflow for software debugging, describe the bug symptoms you observe. The workflow then enforces a four-phase process—investigate, analyze, hypothesize, implement—using tools like grep and web search to gather evidence before any fixes are applied.
Yes, root-cause debugging prevents premature or unsafe code changes by enforcing scope control and governance. It uses pretool freeze checks and plan-mode safeguards to minimize collateral changes, ensuring you validate hypotheses with evidence before modifying code.
Yes, you can use telemetry to improve your debugging workflow over time. The investigation process includes telemetry and contributor mode features designed to capture learnings from your root-cause analysis and share them with your team to prevent recurring outages.
sQVeDiagnose bugs by tracing evidence and generating a BR issue template.
louisfghbvcOrganize project learnings across sessions in a local JSONL database.
EhsaanArkDiagnose software bug root causes through phase-based investigation and code tracing.
TumeloRamaphosaInvestigate software failures through a four-phase evidence-first root-cause workflow.
