debug

Trace call stacks and validate fixes with four-phase debugging.

2|Updated Dec 24, 2025
One-click install
npx skills add https://github.com/hotriluan/alkana-dashboard --skill debug-hotriluan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/hotriluan/alkana-dashboard/tree/main/.opencode/skills/debug
Command: npx skills add https://github.com/hotriluan/alkana-dashboard --skill debug-hotriluan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Debug systematically with root-cause analysis before fixes. Use for bugs, test failures, unexpected behavior, performance issues, call stack tracing, multi-layer validation.

Core Features & Use Cases

  • Four-Phase Debugging: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation.
  • Root Cause Tracing: Trace data flow up the call stack to identify the original trigger.
  • Defense-in-Depth: Validate at entry, business logic, environment, and instrumentation layers.
  • Verification Protocol: Verify fixes with fresh evidence before declaring completion.
  • Red Flags: Stop and restart the process when symptoms mislead.

Quick Start

Begin with Phase 1 to gather evidence and reproduce the issue before attempting any fixes.

Frequently Asked Questions about debug

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

FAQPage Schema
What is systematic debugging and how does it find the root cause of a bug?

Systematic debugging identifies and isolates root causes behind bugs or failures by reproducing the issue, tracing data flow up the call stack, and validating fixes through multi-layer verification before completion.

How do I trace a software bug to its original trigger?

Trace a software bug to its original trigger by following data flow up the call stack during the root cause investigation phase, gathering fresh evidence and reproducing the issue before attempting any fixes.

What's the best way to debug test failures and unexpected behavior systematically?

Debug test failures and unexpected behavior systematically using a four-phase process: root cause investigation, pattern analysis, hypothesis and testing, and implementation, enforcing verification before declaring completion.

When should I restart my debugging process because symptoms are misleading?

Restart your debugging process when symptoms mislead you, identified as red flags, to stop the current trajectory and resume evidence gathering from phase one to ensure accurate root cause isolation.

Does defense-in-depth validation apply to performance issues and integration problems?

Defense-in-depth validation applies to performance issues and integration problems by enforcing checks at entry, business logic, environment, and instrumentation layers to ensure fixes are verified with fresh evidence.

Can I use this systematic debugging approach without any external dependencies?

You can use this systematic debugging approach without external dependencies, as it relies on internal scripts and references to guide four-phase debugging, lineage tracing, and verification protocols across software development.