investigate

Guide root-cause analysis of software issues through a four-phase workflow.

Updated May 14, 2026
One-click install
npx skills add https://github.com/lemig/transcriptor --skill investigate-lemig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/lemig/transcriptor/tree/main/.claude/skills/gstack/investigate
Command: npx skills add https://github.com/lemig/transcriptor --skill investigate-lemig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies root causes of software issues quickly by enforcing a disciplined four-phase flow: investigate, analyze, hypothesize, implement.

Core Features & Use Cases

  • Structured four-phase debugging workflow that reduces time to root cause.
  • Guided prompts and safety hooks to ensure careful, reproducible investigations.
  • Use case: when you see errors, stack traces, or intermittent failures, invoke this skill to trace root cause and propose fixes.

Quick Start

Ask me to investigate a bug by starting the four-phase root-cause analysis.

Frequently Asked Questions about investigate

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

FAQPage Schema
What is a systematic root-cause debugging workflow for software errors?

A systematic root-cause debugging workflow resolves software errors by enforcing a four-phase process: investigate, analyze, hypothesize, and implement, reducing time to identify failures across modules.

How do I troubleshoot intermittent failures and performance regressions across modules?

Troubleshoot intermittent failures and performance regressions by applying a structured four-phase workflow that uses Bash, Read, Grep, and WebSearch to trace root causes and propose fixes safely.

What's the best way to trace unexpected application behavior to its root cause?

The best way to trace unexpected behavior to its root cause is a disciplined workflow that analyzes stack traces and environment states, gating transitions between investigation, hypothesis, and implementation phases.

Can I use this debugging workflow for crashes in different environments?

Yes, this debugging workflow applies to errors, crashes, and unexpected behavior across multiple modules and environments, using safety hooks to ensure careful and reproducible investigations.

How do I start a root-cause analysis for a stack trace?

Start root-cause analysis for a stack trace by invoking the investigation phase, which uses Read and Glob tools to gather context before moving to the analysis and hypothesis stages.