skills.rest
Intension-us
Intension-usOFFICIAL
Explore all skills by this author →
GitHub

investigate

Guide structured debugging workflows to identify root causes of failures.

Updated Apr 3, 2026
Search Tags:#debugging#analysis#pattern#investigate#root-cause#stack-trace
One-click install
npx skills add https://github.com/Intension-us/attention-diagnostic --skill investigate-intension-us
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/Intension-us/attention-diagnostic/tree/main/.claude/skills/gstack/investigate
Command: npx skills add https://github.com/Intension-us/attention-diagnostic --skill investigate-intension-us

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging reduces time to root cause by guiding engineers through four disciplined phases: investigate, analyze, hypothesize, and implement, ensuring fixes address the real problem rather than symptoms.

Core Features & Use Cases

  • Structured root-cause investigation workflow that prompts symptom collection, code analysis, and hypothesis testing.
  • Integrates with code search (grep/read) and change history to pinpoint root cause and prevent regressions.
  • Ideal for errors, stack traces, intermittent failures, or behavior that stopped working and needs a solid post-mortem.

Quick Start

Start by summarizing the symptoms you see, then run the structured investigator to trace back to the root cause.

Frequently Asked Questions about investigate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a stack trace to find the root cause of an error?▼

Debug a stack trace to its root cause by following a structured investigation workflow that collects symptoms, analyzes code, gathers evidence, and tests hypotheses before safely remediating the failure.

What is the best way to systematically debug intermittent failures in a codebase?▼

Systematic debugging of intermittent failures uses a disciplined process of symptom collection, code understanding, evidence gathering, and hypothesis testing to ensure fixes address the real problem rather than just treating symptoms.

How do I investigate unexpected behavior that stopped working across environments?▼

Investigate unexpected behavior across environments by guiding through structured phases: collect symptoms, analyze code with search and change history, test hypotheses, and implement safe remediations to prevent regressions.

Can I use a structured root-cause analysis workflow for code regressions?▼

Structured root-cause analysis workflows integrate with code search and change history to pinpoint the source of regressions, guiding you through symptom collection and hypothesis testing to ensure a solid post-mortem.

Why should I use a hypothesis-driven debugging process instead of patching symptoms?▼

Hypothesis-driven debugging reduces time to root cause by enforcing four disciplined phases—investigate, analyze, hypothesize, and implement—ensuring your fixes address the actual underlying problem rather than temporary symptom patches.

What do I need to start a root-cause debugging session for unexpected code behavior?▼

To start root-cause debugging, summarize the observed symptoms, errors, or stack traces you are encountering, then run the structured investigator to trace the issue back to its underlying cause through evidence and hypothesis testing.

Related Skills

Explore More Software Engineering Skills→
devs6186devs6186

gstack-openclaw-investigate

Diagnose software bugs through a phase-driven debugging workflow and produce debug reports.

Community
Advanced
westnwestn
1

gstack-openclaw-investigate

Guide root cause investigation through a five-phase debugging workflow.

Community
Advanced
simotasimota
68

Scout

Analyze error reports and trace execution flows to identify software bug root causes.

Community
Advanced
htlin222htlin222
77

error-detective

Search and analyze log files and codebases for error patterns and stack traces.

Community
Intermediate