SAMRADDHASHRIVASTAVATECH Error investigation
Turn an error message into a diagnosis: hunt documentation, issue trackers, and community reports in parallel, then synthesize.
When to use
- A cryptic error with no obvious fix.
- An error that exists across versions/environments.
- The user wants a probable cause plus verification steps, not a guess.
Tools used
investigate_error—error(the exact message) with optionaltechcontext.
Workflow
- Quote the exact error string + known tech stack (
tech). investigate_error— it routes across web/docs/GitHub/community coverage.- Cross-check candidate causes against reproducibility (same version? minimal repro?)
- Deliver: likely cause, the fix path, and how to verify it — separating confirmed from reported.
Input schema
{ "error": "str", "tech": "str" }
Output schema
{ "error": "str", "likely_cause": "str", "evidence": "list[{source,url}]", "fixes": "list[str]" }
Security
Never paste logs/error strings containing secrets into search. Report fixes with sources; do not apply community-pasted commands to the user's machine without review.
Related skills
github-research, community-research, web-search, source-analysis