Generate ranked root-cause hypotheses from bug symptoms and code paths.
npx skills add https://github.com/Hoang604/get-thing-done --skill d-inspect
Please help me install this Agent Skill. Skill: d-inspect Source: https://github.com/Hoang604/get-thing-done/tree/main/.claude/skills/d-inspect Command: npx skills add https://github.com/Hoang604/get-thing-done --skill d-inspect
This skill helps engineers diagnose root causes of bugs by analyzing symptoms and tracing code paths to generate ranked hypotheses.
Provide a symptom description at ./.gtd/debug/current/SYMPTOM.md and run the /d-symptom flow to load the symptom and trigger hypothesis generation.
High-intent search queries and answers about installing and using this skill.
You provide a symptom description, and the tool traces relevant code paths to generate ranked root-cause hypotheses. It analyzes the symptoms, evaluates the code, and outputs a documented file containing hypotheses with confidence scores.
The best way to document debugging hypotheses is to generate a structured markdown file that records ranked root-cause hypotheses and their reasoning. This ensures traceability of symptom analysis and code path traversal across your codebase.
Place your symptom description in a designated local markdown file and run the symptom loading flow. This triggers the inspection process, which reads the file, traverses the relevant code paths, and generates ranked hypotheses.
Yes, you can trace code paths and form multiple hypotheses without any external dependencies. The tool operates independently to analyze symptoms, traverse the code, and output a markdown file documenting the ranked root-cause hypotheses.
Ranked confidence scores are needed to prioritize debugging efforts effectively. By scoring each hypothesis based on symptom analysis and code path traversal, you focus on the most probable root causes first, reducing time spent on unlikely code paths.
jMertaConvert ambiguous bug reports into reproducible repros, root-cause explanations, and minimal fixes.
erenisiklarDiagnose root causes of bugs using hypothesis-driven debugging phases.
huyhung9630Generate hypotheses and gather evidence to trace software issues to their root cause.
yumayoDiagnose software defects by analyzing symptoms and investigating the codebase.
