One-click install
npx skills add https://github.com/jangtrinh/demo-Lam --skill ck-debug-jangtrinh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:debug
Source: https://github.com/jangtrinh/demo-Lam/tree/main/.claude/skills/ck-debug
Command: npx skills add https://github.com/jangtrinh/demo-Lam --skill ck-debug-jangtrinh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you debug failing systems and code by forcing root-cause investigation before applying any change, preventing random fixes that create new bugs.

Core Features & Use Cases

  • Root Cause First Method: Applies a strict “no fixes without root cause investigation” workflow to turn symptoms into actionable causes.
  • Layered Validation & Tracing: Uses systematic debugging, backward call-chain tracing, defense-in-depth validation, and stack/log evidence collection.
  • Verification Protocols: Enforces fresh verification evidence before claiming the issue is resolved, including optional frontend verification gates.

Quick Start

Use the skill when you provide the error message and context (what failed, where, and any relevant logs) so it can guide you through root-cause investigation and evidence-backed verification.

Frequently Asked Questions about ck:debug

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

FAQPage Schema
What is the best way to find the root cause of a CI/CD pipeline failure?

To find the root cause of a CI/CD pipeline failure, trace symptoms backward through the call chain and collect stack and log evidence before applying any fixes. This structured root cause investigation prevents random patches that create new bugs.

How do I debug a system incident without making random code changes?

Debug a system incident without random changes by enforcing a strict workflow that requires root cause investigation before fixes. Use backward call-chain tracing and defense-in-depth validation to turn symptoms into actionable causes.

How do I verify a code fix actually resolved an unexpected behavior issue?

To verify a code fix resolved unexpected behavior, enforce fresh verification evidence before claiming the issue is resolved. This includes optional frontend verification gates to ensure the system operates correctly after applying the fix.

Can I use this root cause analysis method for performance diagnostics and log analysis?

Yes, you can use this root cause analysis method for performance diagnostics and log analysis. The structured investigation workflow supports tracing performance degradation and analyzing logs to identify actionable causes.

What context do I need to provide to start debugging a failing system?

To start debugging a failing system, provide the error message, what failed, where it failed, and any relevant logs. This context guides the root-cause investigation and evidence-backed verification process.