skills.rest
Kakarottoooo
KakarottooooCOMMUNITY
Explore all skills by this author →
GitHub

investigate

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

Updated Mar 17, 2026
Search Tags:#testing#investigation#debug#hypothesis#root-cause#reproduction
One-click install
npx skills add https://github.com/Kakarottoooo/onegent --skill investigate-kakarottoooo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/Kakarottoooo/onegent/tree/main/.agents/skills/gstack/investigate
Command: npx skills add https://github.com/Kakarottoooo/onegent --skill investigate-kakarottoooo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging workflow that identifies and documents root causes before applying fixes, reducing repeating defects and downtime.

Core Features & Use Cases

  • Phase-driven investigation: gather symptoms, read code, check recent changes, reproduce, and form testable hypotheses.
  • Hypothesis testing & verification: instrument evidence, validate hypotheses, and decide on the next steps with structured decisions.
  • Comprehensive documentation: produce a root-cause hypothesis, fix plan, regression tests, and verification results to prevent reoccurrence.

Quick Start

Ask questions to gather context and start Phase 1 by collecting symptoms, logs, and reproduction steps.

Frequently Asked Questions about investigate

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

FAQPage Schema
How do I identify the root cause of a bug instead of just fixing symptoms?▼

Root-cause debugging enforces a structured investigation workflow that gathers symptoms, reads code, checks recent changes, and reproduces errors to isolate underlying causes before applying fixes.

What is the best way to document hypotheses and verification steps during troubleshooting?▼

Document hypotheses and verification steps during troubleshooting by logging test outcomes, instrumenting evidence, and recording structured decisions across a four-phase investigation workflow for full traceability.

How do I perform a structured post-mortem analysis across codebases and services?▼

Perform a structured post-mortem analysis by collecting reproduction steps, validating testable hypotheses, and producing comprehensive documentation including fix plans and regression tests to prevent reoccurrence.

Can I use a systematic debugging workflow to reduce repeating defects and downtime?▼

Yes, systematic debugging reduces repeating defects and downtime by enforcing root-cause analysis before fixes, documenting the investigation, and generating regression tests to verify the resolution.

Does structured root-cause investigation work for troubleshooting errors in any software codebase?▼

Structured root-cause investigation applies to debugging software, troubleshooting errors, and performing post-mortem analysis across codebases and services without requiring specific external dependencies.

What are the limitations of fixing bugs before forming testable hypotheses?▼

Fixing bugs before forming testable hypotheses often addresses symptoms rather than root causes, which increases repeating defects and downtime due to a lack of structured evidence validation.

Related Skills

Explore More Software Engineering Skills→
tropekstropeks

investigate

Guide engineers through structured four-phase root-cause debugging from symptoms to verification.

Community
Advanced
qa-amanqa-aman
19

qa-execution

Plan, execute, and document QA test cycles with structured inputs and summaries.

Community
Intermediate
audunstrandaudunstrand

Confidence Honesty

Enforce explicit confidence scoring and evidence audits before presenting conclusions.

Community
Advanced
HemantSudarshanHemantSudarshan

systematic-debugging

Automate root-cause analysis across four systematic debugging workflow phases.

Community
Advanced