Guide root-cause debugging through four investigation phases before proposing fixes.
npx skills add https://github.com/I194/PMTools_2.0 --skill investigate-i194
Please help me install this Agent Skill. Skill: investigate Source: https://github.com/I194/PMTools_2.0/tree/main/.claude/skills/gstack/investigate Command: npx skills add https://github.com/I194/PMTools_2.0 --skill investigate-i194
Systematic debugging with root cause investigation to avoid masking symptoms. The Iron Law: no fixes without root cause. Proactively invoke this skill when the user encounters errors, 500s, stack traces, or unexpected behavior.
Ask Claude to start the investigate cycle to identify the root cause before proposing fixes.
High-intent search queries and answers about installing and using this skill.
Root-cause debugging enforces an Iron Law: no fixes until the actual cause is identified. It guides you through a four-phase investigation cycle to gather symptoms and propose evidence-based fixes rather than masking underlying problems.
Debugging unexpected crashes and 500 errors requires a systematic investigation applying Bash, Grep, and Glob to gather symptoms. You reproduce the issue, analyze the evidence, hypothesize the root cause, and only then implement an evidence-based fix.
To start a systematic investigation workflow for troubleshooting stack traces, invoke the investigate cycle. This initiates a structured four-phase process—investigate, analyze, hypothesize, implement—to analyze errors before applying any code fixes.
Yes, this root-cause analysis method applies to debugging pipeline failures and unexpected system behavior across codebases and systems. It uses WebSearch and AskUserQuestion to gather evidence and reproduce the exact failure state.
Applying code fixes before identifying the root cause masks symptoms and risks introducing new issues. The Iron Law of this debugging methodology mandates evidence-based analysis first, ensuring your fixes resolve the actual underlying cause.
Yes, this debugging approach works without external dependencies or components. It operates independently using standard system tools like Bash, Read, Write, Edit, Grep, and Glob to guide the investigation and implement fixes.
jk278Diagnose software bugs from stack traces and error logs.
zhifengzhang-szGuide structured four-phase debugging to identify root causes of software issues.
mrkhachaturovGuide engineers through phased root-cause investigation and evidence-based debugging.
chadanandaGuide engineers through a four-phase root-cause debugging workflow.
