skills.rest
zillabunny
zillabunnyCOMMUNITY
Explore all skills by this author →
GitHub

investigate

Reproduce a bug, trace its root cause, and document a verified fix plan.

Updated Apr 2, 2026
Search Tags:#debugging#investigate#quality-assurance#root-cause#software-engineering#bug-tracing
One-click install
npx skills add https://github.com/zillabunny/GoblinVolleyball-1.1 --skill investigate-zillabunny
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/zillabunny/GoblinVolleyball-1.1/tree/main/.claude/skills/investigate
Command: npx skills add https://github.com/zillabunny/GoblinVolleyball-1.1 --skill investigate-zillabunny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep debugging for complex bugs is time-consuming and error-prone. This skill enforces a disciplined workflow to reproduce, trace, state root cause, fix, and verify, ensuring that fixes are well-founded and verifiable.

Core Features & Use Cases

  • Phase-driven investigation: reproduce, trace, root-cause statement, fix planning, and verification.
  • Evidence-driven: requires screenshots, logs, or outputs as evidence before advancing phases.
  • Use Case: when a bug is too complex for batch fixes, use investigate to isolate the failing component and craft a minimal, verifiable fix.

Quick Start

Initiate a structured root-cause investigation for a described bug: reproduce, trace, state the root cause, and propose a minimal fix plan.

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 complex software bug?▼

To find the root cause of a complex software bug, you follow a phase-driven investigation to reproduce the issue, trace the failing component, and state the root cause before planning a fix. This ensures verifiable outcomes.

What is the best way to debug CI failures and flaky tests?▼

Debugging CI failures and flaky tests requires a structured investigation to isolate the failing component and craft a minimal, verifiable fix plan. Evidence collection ensures the root cause is accurately identified.

How do I trace a bug from initial reproduction to validation?▼

You trace a bug from reproduction to validation by applying a phase-driven workflow that enforces evidence collection like logs or screenshots at each phase gate before advancing to fix planning and verification.

Can I use this approach for bugs that are too complex for batch fixes?▼

Yes, when a bug is too complex for batch fixes, this structured investigation isolates the specific failing component and guides you through crafting a minimal, verifiable fix plan based on collected evidence.

How do I write a root-cause statement and regression plan for software engineering?▼

Writing a root-cause statement and regression plan requires using a fixed template after evidence collection and phase gates. This enforces verifiable outcomes and documents a verified fix plan for the bug.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

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

Community
Advanced
bostonaholicbostonaholic
8

test-driven-bug-fix

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

Community
Advanced
wangfeivwangfeiv

gstack/qa

Automate web application testing for layout, functionality, accessibility, and performance.

Community
Intermediate
wangrenzhu-olawangrenzhu-ola
2

gh:debug

Trace bugs from trigger to symptom and validate root causes.

Community
Advanced