ck:debug

Diagnose root causes through a four-phase debugging framework with verification.

Updated Feb 27, 2026

Search Tags:#debugging #investigation #logs #tracing #ci-cd #root-cause

Ready to run

npx skills add https://github.com/haidonglethqb/CloudSchool --skill ck-debug-haidonglethqb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ck:debug
Source: https://github.com/haidonglethqb/CloudSchool/tree/main/.qwen/skills/debug
Command: npx skills add https://github.com/haidonglethqb/CloudSchool --skill ck-debug-haidonglethqb

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Provides a disciplined, four-phase framework to diagnose root causes before attempting fixes, preventing ad-hoc patches and data-path confusion.

Core Features & Use Cases

Four-Phase Debugging: Phase 1 Root Cause Investigation, Phase 2 Pattern Analysis, Phase 3 Hypothesis & Testing, Phase 4 Implementation.
Defense-in-Depth and stack-trace instrumentation to capture context at each boundary.
System-wide data collection guidance across logs, CI/CD, databases, and environment signals.
Practical workflows for code, system, and performance incidents with verification before completion.

Quick Start

Describe a bug scenario and apply Phase 1 through Phase 4 to trace, confirm root cause, and implement a verified fix.

Frequently Asked Questions about ck:debug

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

FAQPage Schema

What is a systematic framework for debugging to find a root cause?▼

Systematic debugging uses a four-phase framework to trace root causes before applying fixes. It guides incident handling from data gathering and pattern analysis to hypothesis testing and verified implementation across code and CI/CD environments.

How do I debug issues across code, systems, and CI/CD environments?▼

Debugging across code, systems, and CI/CD environments requires system-wide data collection from logs and databases. You apply a structured four-phase process to investigate patterns, test hypotheses, and verify fixes before completion.

How do I prevent ad-hoc patches when investigating incidents?▼

Preventing ad-hoc patches during incident investigation requires defense-in-depth and stack-trace instrumentation to capture context at each boundary. This disciplined approach ensures you confirm the root cause before implementing any code fixes.

Can I use a structured debugging process for performance incidents?▼

Yes, you can use a structured debugging process for performance incidents. The framework provides practical workflows for code, system, and performance issues, ensuring no completion claims are made without fresh verification evidence.

What is the best way to trace a root cause from logs and environment signals?▼

The best way to trace a root cause from logs and environment signals is following a four-phase debugging framework. It starts with data gathering, analyzes patterns, forms hypotheses, and ends with a verified fix implementation.