skills.rest
Sjdjdiejdrirhdkjej
SjdjdiejdrirhdkjejCOMMUNITY
Explore all skills by this author →
GitHub

debug-phase

Diagnose software bugs systematically to identify root causes and document findings.

Updated Jan 5, 2026
Search Tags:#testing#debugging#logging#root-cause#reproduction#5_whys#error-log
One-click install
npx skills add https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor --skill debug-phase-sjdjdiejdrirhdkjej
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-phase
Source: https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor/tree/main/.claude/skills/debug-phase
Command: npx skills add https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor --skill debug-phase-sjdjdiejdrirhdkjej

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging software issues is often ad hoc, time-consuming, and error-prone. This Skill provides a structured, repeatable approach to diagnose bugs, classify errors, reproduce failures, identify root causes with methods like 5 Whys and binary search, and document findings to prevent recurrence.

Core Features & Use Cases

  • Step-by-step debugging workflow aligned with common development practices.
  • Root-cause analysis templates (5 Whys) and structured reproduction strategies.
  • Documentation guidance for error-log.md and creation of regression tests.

Quick Start

  1. Reproduce the error reliably to establish a baseline.
  2. Classify the error by type and severity, then choose a debugging strategy.
  3. Apply root-cause techniques (5 Whys, hypothesis testing, or binary search) to locate the underlying issue, update tests, and document results in error-log.md.

Frequently Asked Questions about debug-phase

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

FAQPage Schema
How do I find the root cause of a software bug instead of just fixing symptoms?▼

Reproduce the software bug reliably by establishing a baseline, classify the error by type and severity, apply root-cause techniques like 5 Whys or binary search, then implement fixes and document findings in error-log.md to prevent recurrence.

What is the 5 Whys technique for debugging software errors?▼

A structured debugging workflow requires reliable error reproduction to establish a baseline, error classification by type and severity, and applying hypothesis testing or binary search to locate issues and create regression tests for verification.

How do I document debugging findings to prevent recurring software issues?▼

Document debugging findings by creating an error-log.md file and adding regression tests. This structured documentation records root causes, reproduction steps, and fixes, ensuring verified results and preventing the same software errors from recurring.

What's the best way to reproduce errors reliably during software debugging?▼

The best way to reproduce errors reliably during software debugging is to establish a consistent baseline. Structured reproduction strategies provide actionable templates to consistently trigger failures before applying root-cause analysis and implementing fixes.

Related Skills

Explore More Software Engineering Skills→
oxieoxie

debug-phase

Diagnose software errors, isolate root causes, and document fixes.

Community
Intermediate
jk278jk278

debugging-assistant

Diagnose software bugs from stack traces and error logs.

Community
Advanced
allexcdallexcd

autonomous-bug-fixing

Diagnose, reproduce, and fix code defects from bug reports or error logs.

Community
Advanced
Rikinshah787Rikinshah787
5

phantom

Debug software defects using root cause analysis and test automation.

Community
Advanced