skills.rest
heyJordanParker
heyJordanParkerCOMMUNITY
Explore all skills by this author →
𝕏@heyJordanParkerGitHub

debug

Trace root causes of software bugs through a four-phase debugging process.

20|3|Updated Aug 16, 2016
Search Tags:#debugging#defense-in-depth#systematic#tracing#phases#root-cause#bug-fix
One-click install
npx skills add https://github.com/heyJordanParker/dotfiles --skill debug-heyjordanparker
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/heyJordanParker/dotfiles/tree/main/claude/.claude/skills/debug
Command: npx skills add https://github.com/heyJordanParker/dotfiles --skill debug-heyjordanparker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systematically debug bugs by tracing root causes rather than patching symptoms, reducing repeat failures.

Core Features & Use Cases

  • Four-phase systematic debugging framework guiding Root Cause Tracing and defense-in-depth validation.
  • Step-by-step process to observe, reproduce, and analyze data flow to locate original triggers.
  • Use cases include confronting complex multi-component failures, deep stack traces, and inconsistent data leading to bugs.

Quick Start

  1. Load the debugging framework: start by reading references/systematic.md and root-cause-tracing.md.
  2. For a failing test, begin with Phase 1: observe symptom, reproduce, and trace data flow.

Frequently Asked Questions about debug

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

FAQPage Schema
What is root cause tracing and how does it fix bugs systematically?▼

Root cause tracing is a debugging technique that identifies the original trigger of a failure rather than patching surface symptoms. It observes data flow across components to systematically fix bugs and prevent repeat failures.

How do I debug deep stack traces and multi-component failures step by step?▼

Debug deep stack traces using a four-phase systematic framework: observe the symptom, reproduce the error, trace data flow across components, and apply layered defenses before implementing fixes to ensure multi-component failures are resolved.

Can I use this systematic debugging framework for inconsistent data scenarios?▼

Yes, the systematic debugging framework applies to inconsistent data scenarios. It guides you to analyze data flow and locate original triggers, ensuring invalid data conditions are traced to their root cause before fixes are applied.

What's the best way to fix bugs without patching symptoms?▼

The best way to fix bugs without patching symptoms is using a defense-in-depth validation process. It mandates root cause investigation and layered defenses before any code fixes, reducing the likelihood of repeat failures.

Why should I not apply immediate fixes when debugging complex errors?▼

Applying immediate fixes without root cause investigation often patches symptoms rather than resolving the actual bug. The systematic debugging process enforces observation and data flow tracing first to prevent repeat failures.

Does this debugging process require any specific dependencies or frameworks?▼

No specific dependencies are required to use the systematic debugging process. It is a framework-agnostic methodology applicable across software projects for tracing root causes and resolving deep stack errors.

Related Skills

Explore More Software Engineering Skills→
abranjithabranjith

fix

Diagnose software bugs, apply minimal fixes, and add regression tests.

Community
Advanced
romiluz13romiluz13
161

debugging-patterns

Enforce root-cause investigation before applying fixes in debugging workflows.

Community
Advanced
bouwerpbouwerp

root-cause-tracing

Trace errors from symptoms back to original triggers across stack traces and logs.

Community
Advanced
gracefullightgracefullight
46

oma-debug

Reproduces failures, identifies root cause, applies minimal fixes with regression tests.

Community
Advanced