Identify root causes of software bugs using logs and system tools.
npx skills add https://github.com/Faeif/linguaquest --skill investigate-faeif
Please help me install this Agent Skill. Skill: investigate Source: https://github.com/Faeif/linguaquest/tree/main/.claude/skills/gstack/investigate Command: npx skills add https://github.com/Faeif/linguaquest --skill investigate-faeif
Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause.
Describe the failing symptoms and gather logs to initiate root-cause analysis.
High-intent search queries and answers about installing and using this skill.
To identify the root cause of a 500 error or stack trace, systematically gather logs and evidence using a four-phase workflow: investigate, analyze, hypothesize, and implement. This ensures no fixes are applied without understanding the underlying error.
The best way to stop recurring bugs across modules and services is enforcing an iron law of no fixes without root cause analysis. By systematically investigating symptoms and gathering evidence before proposing changes, you prevent superficial patches.
To start debugging unexpected behavior, describe the failing symptoms and gather logs to initiate root-cause analysis. The investigation phase proactively coordinates end-to-end checks to collect the necessary evidence for a hypothesis.
Yes, you can use this workflow for errors spanning multiple services. It applies to unexpected behavior across modules and services, satisfying end-to-end coordination and explicit checks to safely gather evidence and propose fixes.
The root-cause analysis process integrates Bash, Read, Write, Edit, Grep, Glob, AskUserQuestion, and WebSearch. These tools gather evidence, inspect system files, and search for context to accurately identify and propose fixes for bugs.
LuminairPrimeInvestigate software bugs through root-cause analysis and hypothesis testing.
ekrishguptaIdentify and fix root causes of bugs through a four-phase workflow.
jk278Diagnose software bugs from stack traces and error logs.
OneWave-AIReview code for security vulnerabilities, performance bottlenecks, and maintainability issues.
