ck:debug

Debug code and system issues through root cause analysis and verification protocols.

1|1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/Thanh-apero/apero-kit-cli --skill ck-debug-thanh-apero
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:debug
Source: https://github.com/Thanh-apero/apero-kit-cli/tree/main/.claude/skills/ck-debug
Command: npx skills add https://github.com/Thanh-apero/apero-kit-cli --skill ck-debug-thanh-apero

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires scripts/find-polluter.sh, scripts/find-polluter.test.md, scripts/screenshot.js, scripts/console.js, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of debugging systematically by providing a comprehensive framework for root cause analysis before attempting fixes.

Core Features & Use Cases

  • Systematic Debugging: Offers a four-phase framework for debugging: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation.
  • Root Cause Tracing: Helps trace bugs backward through the call stack to find the original trigger.
  • Defense-in-Depth Validation: Validates data at every layer to prevent bugs from occurring.
  • Verification: Ensures that fixes are verified thoroughly before completion claims are made.
  • Use Case: When you encounter a bug in your code or a system issue, this Skill can guide you through the debugging process step by step.

Quick Start

Use the ck:debug skill to begin debugging your code. Follow the systematic approach outlined in the SKILL.md file.

Frequently Asked Questions about ck:debug

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

FAQPage Schema
What is systematic debugging and how does root cause analysis work?

Root cause tracing works by tracing bugs backward through the call stack to find the original trigger before attempting fixes. This systematic debugging approach ensures problems are addressed at their source rather than just treating symptoms.

How do I debug code issues step by step using a systematic approach?

Debug code issues using a four-phase framework: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation. This systematic approach guides you through troubleshooting step by step to ensure problems are addressed at their source.

What's the best way to troubleshoot system issues and prevent recurring bugs?

The best way to troubleshoot system issues is defense-in-depth validation, which validates data at every layer to prevent bugs from occurring. This systematic approach ensures fixes are verified thoroughly before completion.

Does this systematic debugging framework work for both code-level and system-level issues?

Yes, this debugging framework is applicable to various code-level and system-level issues. It provides a comprehensive troubleshooting approach that ensures problems are addressed at their source regardless of the issue's scope.

Why should I verify fixes before claiming debugging is complete?

Verification ensures that fixes are validated thoroughly before completion claims are made. This defense-in-depth approach confirms the root cause has been addressed and prevents the bug from recurring across system layers.