skills.rest
westn
westnCOMMUNITY
Explore all skills by this author →
𝕏@westnGitHub

gstack-openclaw-investigate

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

1|Updated Mar 15, 2026
Search Tags:#debugging#investigation#quality#process#root-cause#software-engineering#bug-fix
One-click install
npx skills add https://github.com/westn/gstack-pi-port --skill gstack-openclaw-investigate-westn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-openclaw-investigate
Source: https://github.com/westn/gstack-pi-port/tree/main/port/gstack/openclaw/skills/gstack-openclaw-investigate
Command: npx skills add https://github.com/westn/gstack-pi-port --skill gstack-openclaw-investigate-westn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, repeatable approach to debugging by guiding users through root cause investigation, pattern analysis, hypothesis testing, and controlled implementation to ensure fixes address the real issue and avoid regressing the system.

Core Features & Use Cases

  • Phase-driven workflow: follows five phases (investigate, analyze, hypothesize, implement, verify) to diagnose and resolve defects.
  • Structured output: promotes a verifiable debug report with symptom, root cause, fix, evidence, and regression test references.
  • Risk-aware execution: emphasizes minimal diffs, regression testing, and escalation when the architecture is unclear.

Quick Start

Describe the observed bug, reproduce it, and record the initial root-cause hypothesis.

Frequently Asked Questions about gstack-openclaw-investigate

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

FAQPage Schema
What is systematic root-cause debugging and when should I use it?▼

Systematic root-cause debugging is a structured approach to diagnosing software bugs by investigating symptoms, testing hypotheses, and verifying evidence before implementing fixes. It applies during debugging sessions, incident investigations, and post-mortem analyses across codebases.

How do I investigate a software bug without causing regressions?▼

To investigate a software bug safely, follow a five-phase workflow: investigate, analyze, hypothesize, implement, and verify. This process enforces minimal diffs, regression testing, and verification of the root cause before applying fixes to avoid destabilizing the system.

What's the best way to structure a post-mortem analysis for an incident investigation?▼

The best way to structure a post-mortem analysis is to generate a verifiable debug report documenting the symptom, root cause, applied fix, supporting evidence, and regression test references. This ensures the investigation remains structured and repeatable.

How do I test root cause hypotheses during a debugging session?▼

To test root cause hypotheses during debugging, describe the observed bug, reproduce it, and record an initial hypothesis. Then analyze patterns and test the hypothesis systematically before moving to controlled implementation and verification phases.

When should I escalate a bug fix during root cause analysis?▼

You should escalate a bug fix during root cause analysis when the system architecture is unclear. Risk-aware execution emphasizes knowing when to escalate rather than forcing a fix that might introduce regressions or misunderstand the codebase structure.

Related Skills

Explore More Software Engineering Skills→
laozhong86laozhong86
1

diagnose

Guide a phase-driven root-cause analysis loop for bugs and performance regressions.

Community
Advanced
viraatdasviraatdas

investigate

Identify bug root causes by collecting symptoms, reading code, and testing hypotheses.

Community
Advanced
I-OnlabsI-Onlabs
3

code-auditor

Audit codebases across architecture, quality, security, and performance to produce prioritized health reports.

Community
Advanced
dsifrydsifry
60

root-cause-tracing

Trace errors backward through call stacks to identify root causes.

Community
Basic