{"enrichment":{"faq":[{"a":"Investigate walks you through a structured methodology to pinpoint what's causing bugs, test failures, build errors, and unexpected behavior. It cycles through characterization, isolation, hypothesis generation, and targeted testing\u2014with escalation to deeper analysis when needed\u2014to diagnose the root cause without applying fixes.","q":"What does Investigate help me do?"},{"a":"Investigate helps you find the answer by systematically debugging and diagnosing unexpected behavior. The skill guides you through isolating the failure, characterizing its symptoms, generating hypotheses about the cause, and running targeted tests to confirm which one is correct\u2014all before you attempt any fix.","q":"Why is my test failing?"},{"a":"Investigate uses a cyclic methodology: first characterize what's broken and how it fails, then isolate which component or code path is responsible, form hypotheses about why it's happening, and test each hypothesis systematically. When standard approaches don't work, Investigate escalates to deeper analysis techniques.","q":"How does Investigate help find the root cause of an error?"},{"a":"Yes. Investigate is designed to handle intermittent and hard-to-reproduce failures by helping you systematically narrow down conditions, timing, and dependencies. It guides you through isolation and hypothesis testing to characterize the failure pattern and identify what triggers it.","q":"Can Investigate troubleshoot intermittent or hard-to-reproduce failures?"},{"a":"Investigate can help diagnose performance issues and slow responses by applying the same structured methodology: characterizing the slowness, isolating which component is the bottleneck, forming hypotheses about the cause, and testing them to confirm the root cause.","q":"Does Investigate investigate performance issues?"},{"a":"Investigate is licensed under the MIT license, which permits free use, modification, and distribution with minimal restrictions.","q":"What is Investigate's license?"}],"shadow_tags":["root-cause-analysis","systematic-debugging","failure-diagnosis","hypothesis-driven","problem-isolation","error-characterization","troubleshooting-workflow","evidence-gathering","defect-investigation"],"summary_rewrite":"Investigate walks you through a structured methodology to pinpoint what's causing bugs, test failures, build errors, and unexpected behavior. It cycles through characterization, isolation, hypothesis generation, and targeted testing\u2014with escalation to deeper analysis when needed\u2014to diagnose the root cause without applying fixes."},"files":[{"bytes":7791,"path":"claude/skills/investigate/SKILL.md","sha256":"994d76d219e566c01825e65dde68a37cc87ddf0657a23eaf4823f19e0e627bc1","url":"https://skillfed.io/files/tobihagemann/turbo/investigate/4abda837/SKILL.md"}],"id":"tobihagemann/turbo/investigate","links":{"html":"https://skillfed.io/tobihagemann/turbo/investigate","md":"https://skillfed.io/tobihagemann/turbo/investigate.md","repo":"https://github.com/tobihagemann/turbo"},"meta":{"agents_supported":["claude-code","codex"],"first_seen":"2026-07-28","forks":29,"language":"Shell","last_updated":"2026-07-27","license":"MIT","name":"investigate","publisher":"tobihagemann","stars":377},"relations":{"categories":["debugging","devops","software-engineering"],"similar":[{"id":"rsmdt/the-startup/debug"},{"id":"dcouple/Pane/investigate"},{"id":"m0n0x41d/haft/h-diagnose"},{"id":"akillness/jeo-skills/diagnose"},{"id":"wshobson/agents/parallel-debugging"},{"id":"Mathews-Tom/armory/debug-investigator"},{"id":"blueberrycongee/termcanvas/investigate"},{"id":"catlog22/Claude-Code-Workflow/investigate"},{"id":"jwilger/agent-skills/debugging-protocol"},{"id":"Dimillian/Skills/bug-hunt-swarm"}]},"slug":{"owner":"tobihagemann","repo":"turbo","skill":"investigate"},"version":"4abda837"}