skills.rest
Yaugourt
YaugourtCOMMUNITY
Explore all skills by this author →
𝕏@YaugourtGitHub

investigate

Identify root causes of bugs by analyzing logs and code paths.

2|2|Updated Dec 1, 2024
Search Tags:#workflow#debug#investigate#code-analysis#root-cause#bug-triage
One-click install
npx skills add https://github.com/Yaugourt/LiquidTerminal_Back --skill investigate-yaugourt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/Yaugourt/LiquidTerminal_Back/tree/main/.agents/skills/gstack/investigate
Command: npx skills add https://github.com/Yaugourt/LiquidTerminal_Back --skill investigate-yaugourt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging with root cause investigation to stop chasing symptoms and deliver durable fixes.

Core Features & Use Cases

  • Four-phase workflow: investigate, analyze, hypothesize, implement to identify root causes.
  • Iron Law: no fixes without root cause; prevents patchwork solutions.
  • Use cases include debugging user-reported errors, stack traces, 500 errors, or unexpected behavior across projects.

Quick Start

Tell me to investigate the latest error by collecting symptoms, reading relevant code paths, and proposing a root-cause hypothesis.

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 bug instead of just fixing symptoms?▼

Debugging stack traces and 500 errors involves systematically collecting symptoms, analyzing logs, and reading relevant code paths to form a root-cause hypothesis before applying an evidence-based fix.

What is the best workflow for debugging unexpected behavior across a codebase?▼

The best workflow for debugging unexpected behavior follows four phases: investigate, analyze, hypothesize, and implement, ensuring you read code paths and reproduce the issue before proposing a minimal patch.

Can I use this approach to debug user-reported errors and 500s?▼

Yes, you can debug user-reported errors and 500s by applying a structured investigation workflow that collects symptoms, reads code paths, checks version history, and locks scope if needed.

Do I need code exploration tools to investigate root causes?▼

Yes, root-cause investigation requires access to code exploration tools, version history, and the ability to generate a debug plan to effectively trace code paths and identify failures.

Why should I avoid patchwork solutions when fixing software bugs?▼

You should avoid patchwork solutions because an iron law of root-cause debugging mandates no fixes without identifying the root cause, which prevents recurring failures and delivers durable fixes.

What limitations exist when locking scope during a bug triage?▼

Locking scope during a bug triage limits the investigation area to prevent expanding the search space, allowing you to focus on analyzing specific recent changes and generating a minimal patch for the root cause.

Related Skills

Explore More Software Engineering Skills→
fabnfabn
1

spacelift:debug

Analyze failed Spacelift run logs to identify error causes.

Community
Advanced
dmitryprg-aidmitryprg-ai
9

bugfix

Automate root-cause debugging and patch deployment with a 6-step workflow.

Community
Intermediate
steadyfallsteadyfall

gstack-openclaw-investigate

Diagnose software defects through structured root-cause investigation workflows.

Community
Advanced
aniruddh2003aniruddh2003
1

speckit.checker

Run static analysis tools to detect security vulnerabilities, type errors, and linting issues.

Community
Intermediate