Guide systematic debugging and root cause analysis of technical bugs.
npx skills add https://github.com/borkweb/skills --skill investigate-borkweb
Please help me install this Agent Skill. Skill: investigate Source: https://github.com/borkweb/skills/tree/main/skills/gstack/investigate Command: npx skills add https://github.com/borkweb/skills --skill investigate-borkweb
This Skill systematically tackles technical debugging with root cause investigation, enabling accurate identification and resolution of bugs.
Start an investigation using 'investigate debug' to begin the root cause analysis of an error.
High-intent search queries and answers about installing and using this skill.
Systematic root cause analysis involves collecting symptoms, reviewing code, and applying investigative phases like data, environment, and performance debugging to accurately identify and resolve technical bugs.
Debugging performance issues across environments requires specialized investigation paths that compare local and CI/CD configurations, tracking system metrics and data flow to isolate bottlenecks.
Yes, systematic troubleshooting diagnoses environmental issues by comparing local versus CI/CD configurations, collecting symptoms, and reviewing code to detect discrepancies causing pipeline failures.
Start an investigation by defining the context and collecting symptoms, then proceed through root cause investigation phases while tracking evidence to resolve the technical bug.
Systematic debugging for complex code analysis relies heavily on accurate symptom collection and evidence tracking; incomplete environmental data or obscured performance metrics can hinder root cause identification.
NTCodingInstrument software with logs and traces to debug runtime behavior.
sumik5Diagnose Next.js 16.0.0+ projects, upgrade versions, and auto-fix errors.
thinking-machines-labCapture training metrics, logtrees, and traces into metrics.jsonl and logtree.json files.
PostHogInstrument SvelteKit applications to report runtime errors to PostHog.
