skills.rest
tan-yong-sheng
tan-yong-shengCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gstack-investigate

Identify and isolate root causes of bugs through a four-phase workflow.

1|1|Updated Mar 5, 2026
Search Tags:#automation#debugging#analysis#grep#investigate#root-cause#websearch
One-click install
npx skills add https://github.com/tan-yong-sheng/GrowChat --skill gstack-investigate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-investigate
Source: https://github.com/tan-yong-sheng/GrowChat/tree/main/.claude/skills/gstack-investigate
Command: npx skills add https://github.com/tan-yong-sheng/GrowChat --skill gstack-investigate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Root-cause debugging with a structured four-phase workflow to stop chasing symptoms and accelerate fixes in complex codebases.

Core Features & Use Cases

  • Four-phase workflow: investigate, analyze, hypothesize, implement.
  • Evidence collection across code, tests, logs using built-in tools like Bash, Read, Write, Edit, Grep, Glob, WebSearch, and AskUserQuestion.
  • Safety and scope enforcement via pre-tool hooks to prevent unsafe or destructive actions.

Quick Start

Describe the bug or issue to start the root-cause investigation using the four-phase workflow.

Frequently Asked Questions about gstack-investigate

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

FAQPage Schema
How do I perform root-cause debugging in a complex codebase?▼

You can collect evidence across codebases and logs using built-in tools like Bash, Read, Grep, Glob, and WebSearch during the root-cause debugging process to systematically gather and validate hypotheses.

What is the best way to automate bug investigation and stop chasing symptoms?▼

A structured four-phase debugging workflow stops you from chasing symptoms by enforcing sequential phases: investigate, analyze, hypothesize, and implement, ensuring fixes target the actual root cause.

Does this debugging workflow prevent destructive actions when running shell commands?▼

During the analyze and hypothesize phases of root-cause debugging, you can use WebSearch to look up external documentation, known issues, or API behaviors to validate your hypotheses.

Can I use grep and web search together to find a root cause?▼

Yes, you can use Grep and Glob to search internal codebases and WebSearch to check external resources simultaneously, gathering comprehensive evidence to validate your root-cause hypotheses.

What are the limitations of automated root-cause analysis?▼

Automated root-cause analysis relies on provided codebases, tests, and logs for evidence; it cannot infer issues outside the accessible scope and requires explicit descriptions of the bug to initiate the investigation.

Related Skills

Explore More Software Engineering Skills→
JoaovsalesJoaovsales
1

debug

Guide bug investigation with reproduction, hypothesis ranking, and fix validation.

Community
Advanced
antriksh-29antriksh-29

investigate

Guide users through a four-phase root-cause investigation before implementing fixes.

Community
Advanced
tomguntomgun

writing-tests

Write and run unit, integration, and acceptance tests for code changes.

Community
Intermediate
thisismynewfmail-uithisismynewfmail-ui

jupyter-live-kernel

Execute multi-line Python code against a live Jupyter kernel with persistent state.

Community
Intermediate