Investigate
Investigate walks you through structured bug diagnosis, starting with hypothesis generation and moving through code inspection, data flow tracing, and controlled experiments to isolate the root cause. It focuses on finding and explaining problems rather than fixing them, and escalates to diagnostic logging only when code inspection alone cannot pinpoint the issue.
Investigate helps you diagnose code issues through hypothesis-driven root cause analysis.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-23
Investigate helps you diagnose code issues through hypothesis-driven root cause analysis. Investigate walks you through structured bug diagnosis, starting with hypothesis generation and moving through code inspection, data flow tracing, and controlled experiments to isolate the root cause. It focuses on finding and explaining problems rather than fixing them, and escalates to diagnostic logging only when code inspection alone cannot pinpoint the issue.
Use it when
- Investigate escalates to diagnostic logging only when code inspection alone cannot pinpoint the issue.
- Yes, Investigate is designed to debug and analyze problems in application behavior.
Install
dcouple/Pane/investigate · repository language: TypeScript
generated, unverified - the skill's exact subdirectory could not be determined; check the repository on GitHub
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I investigate code issues with Investigate?
Investigate guides you through structured bug diagnosis by starting with hypothesis generation, then moving through code inspection, data flow tracing, and controlled experiments to isolate the root cause. The skill focuses on finding and explaining problems rather than fixing them, helping you understand what went wrong before taking corrective action.
What does Investigate do when code inspection alone cannot pinpoint the issue?
Investigate escalates to diagnostic logging only when code inspection alone cannot pinpoint the issue. This systematic approach ensures you exhaust direct code analysis first, making your investigation more efficient and targeted before introducing logging overhead.
Can Investigate help me debug and analyze problems in my application?
Yes, Investigate is designed to debug and analyze problems in application behavior. It helps you systematically explore code behavior, trace data flows, and run controlled experiments to understand how your application is failing and why, supporting both runtime and logic error diagnosis.
How does Investigate help investigate bugs in code?
Investigate helps you find and investigate bugs by walking through hypothesis generation, code inspection, and data flow analysis. Rather than jumping to fixes, it emphasizes understanding the root cause of failures through systematic exploration, making your debugging process more methodical and effective.
What is Investigate's approach to troubleshooting runtime errors?
Investigate addresses runtime errors through structured analysis: generating hypotheses about what went wrong, inspecting relevant code sections, tracing how data flows through your system, and running controlled experiments to confirm your findings. This diagnostic approach isolates root causes before any fixes are attempted.
Does Investigate analyze root causes of failures?
Yes, analyzing root causes of failures is central to Investigate's purpose. The skill moves beyond surface-level symptoms to uncover why failures occur through code inspection, data flow tracing, and systematic experimentation, giving you the understanding needed to address problems at their source.
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Investigate and diagnose code issues or errors”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
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—with escalation to deeper analysis when needed—to diagnose the root cause without applying fixes.
Debug Investigator replaces ad-hoc troubleshooting with structured investigation: capture symptoms, build a reproducible feedback loop, analyze evidence from stacktraces and logs, generate ranked hypotheses, and design bisection strategies. Use it for non-obvious bugs—intermittent failures, performance regressions, or issues requiring systematic root cause analysis—where native debugging falls short.
Investigate guides you through structured debugging in five phases, from evidence collection to verified fix. It enforces the Iron Law principle—never fix without a confirmed root cause—using pattern analysis, hypothesis testing with a 3-strike escalation rule, and regression coverage. Output includes a machine-readable debug report with the full evidence chain.
This skill enforces a disciplined debugging process: establish a tight feedback loop that reproduces the exact symptom, gather evidence across system boundaries, trace data flow to its source, and form testable hypotheses before proposing any fix. By completing each phase sequentially—root cause investigation, pattern analysis, hypothesis testing, and verification—you eliminate guesswork and prevent quick patches from masking deeper issues.
team-frontend-debug orchestrates a multi-role team for frontend quality assurance, routing feature lists to a testing pipeline or bug reports to a debugging pipeline. Both flows leverage Chrome DevTools MCP for browser inspection, DOM analysis, console monitoring, and performance tracing. The coordinator role parses your input, spawns specialized workers (tester, reproducer, analyzer, fixer, verifier), and manages progress across phases.
Issue Management provides a menu-driven interface for tracking and organizing issues through the `ccw issue` CLI. Create, view, edit, delete, and bulk-update issues while filtering by status, priority, or other criteria—with automatic archiving of completed items.
More skills bug-fix-tdd (Apache-2.0) · Debugging (unlicensed)