skills.rest
aicodepro
aicodeproOFFICIAL
Explore all skills by this author →
GitHub

gstack-openclaw-investigate

Diagnoses bugs through phased root cause investigation before applying verified fixes.

Updated Jun 22, 2026
Search Tags:#debugging#bug fix#root cause analysis#stack trace#hypothesis testing#git history#regression test
One-click install
npx skills add https://github.com/aicodepro/ai-agent-nexi --skill gstack-openclaw-investigate-aicodepro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-openclaw-investigate
Source: https://github.com/aicodepro/ai-agent-nexi/tree/main/agent/skills/gstack/openclaw/skills/gstack-openclaw-investigate
Command: npx skills add https://github.com/aicodepro/ai-agent-nexi --skill gstack-openclaw-investigate-aicodepro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents whack-a-mole debugging by enforcing root cause investigation before any fix, so errors, stack traces, and regressions get resolved at the source instead of patched at the symptom. ## Core Features & Use Cases - Five-phase debugging workflow: root cause investigation, pattern analysis, hypothesis testing, minimal implementation, and verification with a structured debug report. - Guardrails against bad fixes: a 3-strike hypothesis rule, red-flag detection, blast-radius warnings for fixes touching more than 5 files, and mandatory regression tests. - Use Case: When a user reports an intermittent production error with a stack trace, the skill traces the code path, checks recent git history, tests a hypothesis with temporary logging, applies a minimal fix, and writes a regression test plus a dated debug report. ## Quick Start Ask the assistant to investigate and find the root cause of the error or stack trace you are seeing before making any code changes.

Frequently Asked Questions about gstack-openclaw-investigate

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

FAQPage Schema
How do I debug an error systematically instead of guessing fixes?▼

Follow a phased approach: collect symptoms and stack traces, trace the code path, check recent git changes, form a testable root cause hypothesis, and verify it with logging before writing any fix. Only then apply a minimal change with a regression test.

What is root cause analysis in software debugging?▼

Root cause analysis identifies the actual underlying defect rather than the visible symptom. It involves reproducing the bug, tracing data flow, checking recent changes, and confirming a specific hypothesis with evidence before modifying code.

How do I write a regression test for a bug fix?▼

Write a test that fails without the fix and passes with it, proving both that the test is meaningful and the fix works. Then run the full test suite to confirm no other behavior regressed.

What should I do when multiple fix attempts fail?▼

After three failed hypotheses, stop and question the architecture rather than guessing again. Escalate for human review, add instrumentation to catch the bug next time, or continue only with a clearly described new hypothesis.

When is a bug fix considered too large?▼

A fix touching more than five files has a large blast radius for a bug fix and should be flagged before proceeding. The goal is the smallest diff that eliminates the root cause without refactoring adjacent code.

Related Skills

Explore More Software Engineering Skills→
ilove323ilove323

debug

Diagnose software failures and generate a structured debugging report.

Community
Intermediate
gyarragyarra

s-end-session

Save conversation memories, update GitHub issues, and generate session summaries.

Community
Intermediate
jammindevjammindev

bug

Reproduce software bugs, add failing regression tests, and verify fixes.

Official
Advanced
UtsavBalar1231UtsavBalar1231
1

debugging

Diagnose runtime failures through hypothesis ranking, instrumentation, and verified fixes.

Community
Intermediate