ck:debug

Enforce root-cause investigation before applying fixes to bugs and system issues.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/hotriluan/alkana_web --skill ck-debug-hotriluan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:debug
Source: https://github.com/hotriluan/alkana_web/tree/main/.opencode/skills/ck-debug
Command: npx skills add https://github.com/hotriluan/alkana_web --skill ck-debug-hotriluan

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

ck:debug provides a structured framework for diagnosing bugs and system issues by enforcing root-cause investigation before any fix. It guides teams through data collection, pattern analysis, and rigorous verification to prevent regression and wasted effort.

Core Features & Use Cases

  • Systematic Debugging: Four-phase process to trace issues from symptoms to root cause.
  • Multi-layer Validation: Defense-in-depth checks across entry, business logic, environment, and instrumentation.
  • Investigation Toolkit: References for debugging methodologies, log/CI analysis, and reporting standards.
  • Collaboration & Tracking: Task-like workflow guidance for coordinating multi-step investigations.

Quick Start

Start a debugging session by outlining the incident and following the four-phase process to identify root cause before applying any fixes.

Frequently Asked Questions about ck:debug

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

FAQPage Schema
What is root-cause debugging and why is it needed before fixing system issues?

Root-cause debugging systematically traces issues from symptoms to their actual origin across code, tests, and deployments before applying fixes. It is needed to prevent wasted effort and ensure the underlying problem is resolved.

How do I start a systematic debugging investigation for a software incident?

To start a systematic debugging investigation, outline the incident and follow a structured four-phase process. This enforces data collection, pattern analysis, and rigorous verification to identify the root cause before applying fixes.

What's the best way to analyze CI-CD logs and tracing data to find a bug?

The best way to analyze CI-CD logs and tracing data is using a defense-in-depth investigation framework. This applies multi-layer validation checks across entry points, business logic, and instrumentation to trace the issue.

Can I use a structured debugging process for multi-step investigations across deployments?

Yes, you can use a structured debugging process for multi-step investigations. It provides task-like workflow guidance and reporting standards, enabling teams to coordinate complex root-cause investigations across deployments.

Why do my bug fixes keep causing regressions in production systems?

Bug fixes cause regressions when applied without identifying the root cause first. Enforcing systematic root-cause investigation and rigorous verification before fixes validates defense-in-depth checks across the system to prevent regressions.