skills.rest
jagreehal
jagreehalCOMMUNITY
Explore all skills by this author →
Website𝕏@jagreehalGitHub

debugging-methodology

Enforce instrumentation and data-driven root-cause analysis before proposing fixes.

3|1|Updated Jan 4, 2026
Search Tags:#debugging#logging#observability#tracing#instrumentation#OpenTelemetry#root-cause-analysis
One-click install
npx skills add https://github.com/jagreehal/jagreehal-claude-skills --skill debugging-methodology-jagreehal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-methodology
Source: https://github.com/jagreehal/jagreehal-claude-skills/tree/main/skills/debugging-methodology
Command: npx skills add https://github.com/jagreehal/jagreehal-claude-skills --skill debugging-methodology-jagreehal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evidence-based debugging discipline that stops guessing and requires instrumentation, logging, and data-driven analysis to identify root causes quickly.

Core Features & Use Cases

  • Instrumented Debugging: Add instrumentation at decision points and log outcomes to reveal root causes.
  • Evidence-Based Decisions: Use traces and logs to form testable hypotheses with minimal changes.
  • Wide Applicability: Effective during bug investigations, test failures, and unexpected behavior across services.

Quick Start

Begin by identifying the symptom, add instrumentation per the protocol, capture logs and traces, then form a hypothesis based on observed data. Use structured logging and optional OpenTelemetry tracing to connect events across steps. Iterate with one-change-at-a-time until the root cause is established.

Frequently Asked Questions about debugging-methodology

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

FAQPage Schema
How do I use structured logging and tracing for root cause analysis?▼

Root cause analysis with structured logging and tracing requires instrumenting decision points to capture data, forming testable hypotheses from observed logs, and iterating with one change at a time until the cause is established.

What is evidence-based debugging and when do I need it?▼

Evidence-based debugging stops guessing by enforcing instrumentation and data-driven analysis to identify root causes. It is needed during bug investigations, test failures, or unexpected behavior across software services.

How do I add instrumentation for debugging without changing too much code?▼

Add instrumentation at decision points and log outcomes using minimal changes, then capture logs and optional OpenTelemetry traces to connect events across steps and reveal root causes.

Does this debugging methodology work with OpenTelemetry?▼

Yes, it supports optional integration with OpenTelemetry tracing to connect events across steps and guide investigation through traceable decision points.

Why does my test failure keep happening even after proposed fixes?▼

Fixes fail without evidence because guessing bypasses root causes. This methodology enforces capturing logs and traces first, forming data-driven hypotheses, and iterating one change at a time until the root cause is established.

Related Skills

Explore More Software Engineering Skills→
berksunduriberksunduri
23

golang-observability

Instrument Go services with structured logging, Prometheus metrics, OpenTelemetry tracing, and pprof profiling.

Community
Advanced
derHakenderHaken
437

systematic-debugging

Trace data flow and apply a four-phase process to fix root causes.

Community
Advanced
williamzujkowskiwilliamzujkowski
17

monitoring-observability

Diagnose performance degradation in distributed systems using Prometheus, Grafana, and OpenTelemetry.

Community
Advanced
claudcherejiclaudchereji

performance-monitor

Monitor and analyze system-wide performance metrics for distributed agent systems.

Community
Advanced