skills.rest
CraftsMan-Labs
CraftsMan-LabsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Trace bugs to their original trigger using defense-in-depth analysis.

33|6|Updated Oct 9, 2025
Search Tags:#testing#debugging#defense-in-depth#traceability#phases#root-cause#stack-trace
One-click install
npx skills add https://github.com/CraftsMan-Labs/SimpleAgents --skill systematic-debugging-craftsman-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/CraftsMan-Labs/SimpleAgents/tree/main/.opencode/skills/systematic-debugging
Command: npx skills add https://github.com/CraftsMan-Labs/SimpleAgents --skill systematic-debugging-craftsman-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Debugging provides a disciplined framework to diagnose bugs, preventing symptom-focused fixes by requiring root-cause investigation and evidence-driven decision making.

Core Features & Use Cases

  • Phase-driven methodology with Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation to ensure robust fixes.
  • Defense-in-depth guidance including multiple validation layers and stack-trace instrumentation to prevent regression and improve observability.
  • Real-world risk reduction: faster debugging cycles, higher first-time fix rates, and clearer traceability across components.

Quick Start

Apply the systematic debugging process to investigate the root cause of a failing test or bug in the current project.

Frequently Asked Questions about systematic-debugging

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 the symptom?▼

To find a root cause, apply a phased debugging methodology that traces the bug to its original trigger, gathers stack-trace evidence, and validates the fix across multiple layers to prevent symptom-driven patches.

What is a defense-in-depth approach to debugging?▼

A defense-in-depth approach to debugging uses multiple validation layers and stack-trace instrumentation to investigate bugs, ensuring structured data tracing and preventing regression through source-level fixes with validated tests.

How do I debug a failing test across different software components?▼

Debug a failing test by tracing structured data across software components, documenting the root cause, performing pattern analysis, and validating source-level fixes with tests to ensure clear traceability.

What is the best way to structure a debugging workflow for unexpected behavior?▼

The best way to structure debugging is a phase-driven methodology: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation, ensuring evidence-driven decision making for unexpected behavior.

When should I use stack-trace instrumentation for bug investigation?▼

Use stack-trace instrumentation during bug investigation to improve observability and gather evidence, enabling structured data tracing that targets the original trigger of test failures or unexpected software behavior.

Can I use this systematic debugging process for any type of software bug?▼

Yes, this systematic debugging process targets any bug, test failure, or unexpected behavior across software components, requiring evidence gathering and phased analysis to implement validated source-level fixes.

Related Skills

Explore More Software Engineering Skills→
mopeyjellyfishmopeyjellyfish
1

debug

Reproduce bugs from evidence and prove root causes with red signals.

Community
Advanced
lv7devlv7dev

Root Cause Tracing

Trace call stacks backward to identify original bug triggers.

Community
Advanced
NeuveAINeuveAI
1

debug-agent

Identify bug root causes by collecting NDJSON logs and testing hypotheses.

Official
Advanced
JansenAnalyticsJansenAnalytics
5

error-monitor

Monitor application logs and stderr to detect errors, crashes, and exceptions.

Community
Intermediate