Diagnose software issue root causes through structured evidence-gathering phases.
npx skills add https://github.com/wodeh/gstack-kimi --skill investigate-wodeh
Please help me install this Agent Skill. Skill: investigate Source: https://github.com/wodeh/gstack-kimi/tree/main/investigate Command: npx skills add https://github.com/wodeh/gstack-kimi --skill investigate-wodeh
Systematic debugging with root cause investigation enables teams to identify the true cause of issues rather than applying quick fixes. It guides responders through a repeatable, phase-driven workflow to move from observation to root-cause resolution.
To begin, say 'investigate this issue' to start the root-cause analysis workflow.
High-intent search queries and answers about installing and using this skill.
Root-cause debugging uses a structured workflow to collect evidence and trace fault paths, moving from observation to resolution. It structures problem-solving into investigate, analyze, hypothesize, and implement phases to locate true underlying causes.
Debugging flaky behavior requires gathering evidence using deterministic tooling like Bash probes and Grep to trace fault paths across code and configurations. A structured investigation workflow guides responders through systematic hypothesis testing to diagnose intermittent issues.
Yes, Bash-based probes are used to gather evidence and test hypotheses during root-cause analysis. The workflow supports deterministic tooling including Bash, Read, Write, Edit, Grep, and Glob to safely collect data and trace faults.
Start an investigation by initiating the root-cause analysis workflow to collect evidence and trace fault paths. The process moves through structured phases of investigation, analysis, hypothesis testing, and implementation to guide responders from observation to resolution.
Yes, optional web searches can corroborate hypotheses during root-cause analysis. Alongside deterministic tooling like Bash probes and file operations, web searches help verify findings when tracing fault paths and diagnosing complex software issues across deployments.
Use a structured debugging workflow when bugs, errors, or flaky behavior occur and require true root-cause identification rather than quick fixes. It is applicable across code, deployments, and configurations where systematic evidence collection and hypothesis testing are needed.
pagerguildConfigure OpenTelemetry tracing, metrics, and logs for Microsoft Agent Framework agents.
aist-ai-sastDiagnose MCP regression failures and implement durable fixes across test suites.
Chang-Shih-YungAggregate type checker, linter, and test results into a 0-10 composite score.
SethyPagnaAttach interactive debuggers to Python processes for breakpoint-driven tracing.
