Guide root-cause debugging of software defects through symptom collection and hypothesis testing.
npx skills add https://github.com/kitfunso/omniskill --skill investigate-kitfunso
Please help me install this Agent Skill. Skill: investigate Source: https://github.com/kitfunso/omniskill/tree/main/skills/investigate Command: npx skills add https://github.com/kitfunso/omniskill --skill investigate-kitfunso
Systematically debugging software by guiding root-cause investigation rather than chasing symptoms.
Start a root-cause debugging session by collecting symptoms, reading relevant code paths, and locking the scope before forming hypotheses.
High-intent search queries and answers about installing and using this skill.
Structured root-cause debugging is a systematic workflow that eliminates guesswork by investigating software defects rather than chasing symptoms. You need it for crashes, failing integrations after merges, and unexpected runtime errors.
To debug without guessing, follow a phase-based workflow: collect symptoms, read relevant code paths, lock the scope, and form hypotheses for testing. This investigative flow ensures reproducible bug-fix sessions across code changes and runtime errors.
The best way to troubleshoot failing integrations is a structured investigation flow. Start by collecting symptoms, inspecting the changed code paths, locking the scope to the merge impact, and systematically testing hypotheses to find the root cause.
Yes, this structured debugging approach applies directly to unexpected runtime behavior. It guides you through symptom collection and code inspection, locking the scope before forming hypotheses to resolve the issue systematically.
Interactive decision making during code analysis uses AskUserQuestion to prompt for input when information is insufficient. This ensures the investigation workflow maintains accuracy by gathering needed context before proceeding with hypothesis testing.
a-ariffTrace bugs backward from symptoms to identify root causes.
dmae97Guide bug resolution from reproduction evidence to root-cause analysis and minimal code changes.
eduardo-slReview Go code for unsafe concurrency patterns and goroutine lifecycle issues.
OneWave-AIReview code for security vulnerabilities, performance bottlenecks, and maintainability issues.
