Generate and test debugging hypotheses across code, logs, and external research.
npx skills add https://github.com/thoreinstein/opencode-config --skill debug-thoreinstein
Please help me install this Agent Skill. Skill: debug Source: https://github.com/thoreinstein/opencode-config/tree/main/skill/debug Command: npx skills add https://github.com/thoreinstein/opencode-config --skill debug-thoreinstein
Debugging complex software issues can be time-consuming and error-prone. This Skill guides engineers through structured hypothesis generation, parallel investigations, and documented verification, helping teams converge on root causes and maintain knowledge in Obsidian.
Start a new debugging session by describing the symptoms and environment to trigger the investigation workflow.
High-intent search queries and answers about installing and using this skill.
Debugging inconsistent runtime errors involves generating and testing hypotheses across code paths, logs, and data flows. This Skill runs parallel investigation tracks for codebase exploration and external research to isolate root causes faster.
Hypothesis-driven debugging systematically generates, ranks, and tests hypotheses against collected evidence like logs and code observations. It orchestrates parallel investigations to converge on root causes methodically.
Yes, you can use this workflow for failing tests and deployment issues. It applies to software issues across codebases, services, and deployments, collecting evidence to verify hypotheses for any runtime error or test failure.
Obsidian is used for evidence collection and documentation, storing debugging narratives and collected metrics for traceable knowledge. It enables teams to maintain documented verification of root cause analysis.
The best way to analyze logs and code simultaneously is using parallel agent orchestration. This Skill runs codebase exploration, code analysis, and external research tracks at the same time to accelerate resolution.
To start a structured debugging session, describe the symptoms and environment of your software issue. This triggers the investigation workflow, which automates hypothesis generation and parallel evidence collection across code and logs.
hawkyreDiagnose and fix software bugs using hypothesis-driven analysis and minimal fixes.
abhattacherjeeCapture and organize error incidents as reusable Obsidian notes.
kriegcloudDecompose complex codebase questions into parallel exploration tracks with cited findings.
fysoul17Trace software bugs to root causes using git history and structured reasoning.
