skills.rest
ibalasite
ibalasiteCOMMUNITY
Explore all skills by this author →
GitHub

investigate

Diagnose software bugs and runtime errors with root cause analysis and regression tests.

Updated Mar 29, 2026
Search Tags:#debugging#telemetry#root-cause#bug-fix#regression-testing#scope-freeze
One-click install
npx skills add https://github.com/ibalasite/gstack --skill investigate-ibalasite
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/ibalasite/gstack/tree/main/investigate
Command: npx skills add https://github.com/ibalasite/gstack --skill investigate-ibalasite

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically discover the root cause of software bugs, avoid symptom-only fixes, and produce verifiable repairs so regressions do not return.

Core Features & Use Cases

  • Four-phase workflow: investigate, analyze, hypothesize, implement — guides you from symptom to proven fix.
  • Scope freeze checks: prevents unrelated edits by locking the narrowest directory during debugging.
  • Hypothesis testing and verification: add temporary logs or assertions, reproduce failures, write regression tests, and run the full test suite.
  • Use case: reproduce an intermittent production error, trace it to a single failing module, add a targeted fix plus a regression test, and verify no other tests regress.

Quick Start

Run the investigate skill when you see a failing test or runtime error, for example say: /investigate to collect logs, grep the codebase, form a root cause hypothesis, and propose a verified fix.

Frequently Asked Questions about investigate

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

FAQPage Schema
How do I find the root cause of a software bug instead of just fixing the symptom?▼

Root cause analysis for software bugs requires systematically collecting evidence, reproducing failures, inspecting source code, and testing hypotheses. A structured debugging workflow isolates the true origin of runtime errors.

What is the best way to debug an intermittent production error that is hard to reproduce?▼

To debug an intermittent production error, collect telemetry and runtime logs, add temporary assertions, and attempt to reproduce the failure conditions. Structured hypothesis testing traces the error to a specific failing module.

How do I prevent unrelated code changes while fixing a regression failure?▼

Prevent unrelated code changes during regression testing by applying scope freeze checks. This locks the narrowest directory needed for debugging, ensuring the bug fix avoids unintended edits elsewhere in the codebase.

How do I verify a bug fix so the same runtime error does not return?▼

Verify a bug fix permanently by writing a regression test that captures the failure, running the full test suite, and confirming no other tests regress. This structured verification proves the root cause is resolved.

What steps should I follow to isolate a failing module during a test-suite regression?▼

Isolate a failing module during a test-suite regression by inspecting source code, forming a root cause hypothesis, adding targeted logs, and reproducing the failure. A four-phase workflow of investigate, analyze, hypothesize, and implement guides this process.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
igij01igij01

bug-fix-and-ship

Automate bug fixes from structured reports to verified source changes.

Community
Advanced
bostonaholicbostonaholic
8

test-driven-bug-fix

Reproduce, isolate, fix, and verify software defects using test-driven methodology.

Community
Advanced
TheBushidoCollectiveTheBushidoCollective
187

debugging

Diagnose software bugs through evidence collection and hypothesis testing.

Official
Advanced