skills.rest
JeremiahEllington
JeremiahEllingtonCOMMUNITY
Explore all skills by this author →
GitHub

investigate

Diagnose root causes of bugs through structured investigation of symptoms and code paths.

Updated Apr 6, 2026
Search Tags:#debug#trace#investigate#code-analysis#root-cause#bug
One-click install
npx skills add https://github.com/JeremiahEllington/NoahEllington --skill investigate-jeremiahellington
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/JeremiahEllington/NoahEllington/tree/main/.claude/skills/investigate
Command: npx skills add https://github.com/JeremiahEllington/NoahEllington --skill investigate-jeremiahellington

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and diagnose root causes of bugs by guiding a structured investigation through symptoms, traces, and code paths.

Core Features & Use Cases

  • Phase-driven debugging that traces from user reports to underlying causes.
  • Cross-checks changes and evidence to avoid premature fixes.
  • Use cases include errors, stack traces, regressions, and intermittent failures reported by users or monitors.

Quick Start

Describe the bug and ask me to investigate the root cause before proposing a 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 bug instead of just patching the symptom?▼

Root-cause debugging requires tracing symptoms through code paths and stack traces to the underlying cause. This Skill guides a structured four-phase investigation—investigate, analyze, hypothesize, implement—with guardrails to prevent premature fixes and ensure reliable resolutions.

What is the best way to debug intermittent failures reported by automated monitors?▼

Debugging intermittent failures involves cross-checking reported symptoms, traces, and recent code changes. This Skill applies a phase-driven workflow that surfaces testable hypotheses from monitor reports, ensuring you address the actual regression rather than applying a quick patch.

How do I stop repeating bugs from recurring in my codebase?▼

Repeating bugs often stem from unaddressed root causes. This Skill diagnoses regressions and errors by guiding a structured investigation through symptoms and traces, enforcing a disciplined workflow that surfaces testable hypotheses for a reliable fix.

Can I use a structured debugging workflow for diagnosing stack traces and user-reported errors?▼

Yes, this Skill is applicable to errors, stack traces, and regressions reported by users or monitors. It guides a structured investigation through symptoms and code paths, cross-checking evidence to avoid premature fixes and deliver reliable resolutions.

Why does fixing a bug too quickly sometimes cause the same issue to reappear?▼

Quick patches often address symptoms rather than the underlying root cause. This Skill prevents repeating bugs by enforcing a four-phase investigation workflow with guardrails, ensuring you hypothesize and test the actual code path failure before implementing a fix.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

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

Community
Advanced
tomguntomgun

fixing-bugs

Reproduce bugs with regression tests and apply minimal root-cause fixes.

Community
Intermediate
acartineacartine
1

investigate

Trace runtime failures with file:line citations before proposing fixes.

Community
Advanced
AtharvaN16AtharvaN16

systematic-debugging

Guide debugging through root cause investigation, pattern analysis, hypothesis testing, and implementation.

Community
Advanced