skills.rest
tmcfarlane
tmcfarlaneCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debugging

Guide systematic root-cause investigation of software bugs through four defined phases.

105|12|Updated Feb 7, 2026
Search Tags:#debugging#systematic#root-cause#software-engineering#open-telemetry#phase-based#trace-analysis
One-click install
npx skills add https://github.com/tmcfarlane/oh-my-cursor --skill debugging-tmcfarlane
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/tmcfarlane/oh-my-cursor/tree/main/skills/debugging
Command: npx skills add https://github.com/tmcfarlane/oh-my-cursor --skill debugging-tmcfarlane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging helps engineers identify and fix root causes rather than applying symptom fixes, reducing wasted time and rework.

Core Features & Use Cases

  • Four-phase debugging framework (Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation) to guide thorough investigation.
  • Best-practice templates and evidence-gathering guidance to reproduce issues reliably and avoid guesswork.
  • Guidance for distributed/multi-service debugging with tracing and instrumentation strategies.

Quick Start

Follow Phase 1: identify the symptom, reproduce it reliably, gather evidence, and then proceed to Phase 2.

Frequently Asked Questions about debugging

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

FAQPage Schema
What is the best way to debug complex software bugs without guessing at solutions?▼

Systematic debugging organizes root-cause investigation into four defined phases: symptom identification, pattern analysis, hypothesis testing, and implementation, ensuring fixes are evidence-based and reproducible.

How do I diagnose root causes in distributed multi-service systems?▼

Diagnose distributed systems by applying trace analysis and instrumentation strategies, gathering evidence across services to reproduce issues reliably and identify root causes in multi-component environments.

How do I start a systematic root-cause investigation for a runtime failure?▼

Begin root-cause investigation in Phase 1 by identifying the specific symptom, reproducing it reliably, and gathering evidence using structured templates before analyzing patterns in Phase 2.

Can I use this systematic debugging approach for flaky tests and development-time defects?▼

Yes, this systematic debugging framework applies across runtime failures, development-time defects, flaky tests, and multi-component systems by enforcing structured evidence gathering and hypothesis testing.

Why does my software fix only address symptoms instead of the root cause?▼

Symptom fixes occur when engineers skip pattern analysis and hypothesis testing; systematic debugging enforces a four-phase framework with evidence-gathering templates to ensure reproducible root-cause fixes.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

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

Community
Advanced
galangryandanagalangryandana
20

systematic-debugging

Enforce a four-phase process for root-cause debugging before proposing fixes.

Community
Advanced
openeuler-mirroropeneuler-mirror
3

root-cause-localization

Correlate logs, trace spans, and dependency graphs to output structured JSON root cause reports.

Official
Advanced
MMXCMMXC

systematic-debugging

Guide four-phase debugging from investigation through implementation.

Community
Advanced