debug-phase

Name: debug-phase
Availability: InStock
Author: DYAI

Classify debugging issues and document root-cause analysis with 5 Whys.

Updated Feb 14, 2026

Search Tags:#debugging #reproduction #root-cause-analysis #5-whys #regression-testing #error-log

Ready to run

npx skills add https://github.com/DYAI2025/MOD_shark-engine --skill debug-phase-dyai2025

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug-phase
Source: https://github.com/DYAI2025/MOD_shark-engine/tree/main/sharkengine/.claude/skills/debug-phase
Command: npx skills add https://github.com/DYAI2025/MOD_shark-engine --skill debug-phase-dyai2025

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Structured debugging workflows to diagnose errors, identify root causes, reproduce issues reliably, and document fixes to prevent recurrence across projects.

Core Features & Use Cases

Error classification framework with type and severity matrices.
Root-cause analysis techniques (5 Whys) and structured reproduction planning.
Guidance for documenting investigations in error-log.md and for creating regression tests.
Templates and checklists to standardize post-mortems and prevention.

Quick Start

Identify a failing scenario, apply 5 Whys to locate the root cause, reproduce the issue, and document the investigation steps and fixes 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 identify the root cause of a software bug systematically?▼

To identify the root cause of a software bug systematically, apply the 5 Whys analysis technique to trace the issue back to its origin, classify the error by type and severity, and document the investigation in a structured error log.

What is the 5 Whys method for root-cause analysis in debugging?▼

The 5 Whys method is a root-cause analysis technique that helps locate the underlying cause of an error by repeatedly asking why an issue occurs, moving beyond surface symptoms to build structured reproduction steps and document the investigation.

How do I write a step-by-step reproduction plan for an error log?▼

Writing a step-by-step reproduction plan for an error log requires documenting the exact sequence of actions that trigger the failure, classifying the issue using an error severity matrix, and recording the details in error-log.md.

How do I create regression tests to prevent bug recurrence across projects?▼

To create regression tests and prevent bug recurrence across projects, follow actionable guidance to design tests based on your structured reproduction steps, standardize post-mortems with checklists, and document the fixes in the error log.

Does structured debugging work for complex issues without specific dependencies?▼

Structured debugging works effectively for complex issues without specific dependencies by using an error classification framework with type and severity matrices to quickly identify and diagnose errors across any project environment.