skills.rest
TNHoang2708
TNHoang2708COMMUNITY
Explore all skills by this author →
GitHub

ck:debug

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

1|Updated Jun 16, 2026
Search Tags:#debugging#root cause analysis#systematic debugging#system investigation#performance diagnostics
One-click install
npx skills add https://github.com/TNHoang2708/Gym_Ver2 --skill ck-debug-tnhoang2708
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:debug
Source: https://github.com/TNHoang2708/Gym_Ver2/tree/main/.claude/skills/ck-debug
Command: npx skills add https://github.com/TNHoang2708/Gym_Ver2 --skill ck-debug-tnhoang2708

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?

The ck:debug skill addresses the challenge of debugging complex issues in software and systems by providing a systematic approach with root cause analysis.

Core Features & Use Cases

  • Systematic Debugging Framework: Offers a four-phase framework for debugging, ensuring root cause investigation before fixes.
  • Root Cause Tracing: Helps trace bugs backward through call stack to find the original trigger.
  • Defense-in-Depth Validation: Validates data at every layer to make bugs structurally impossible.
  • Verification: Ensures no completion claims without fresh verification evidence.
  • Investigation Methodology: Provides a structured five-step process for system-level issues.
  • Log & CI/CD Analysis: Collects and analyzes logs and CI/CD pipelines for diagnosis.
  • Performance Diagnostics: Identifies bottlenecks and analyzes query performance.
  • Reporting Standards: Defines structured diagnostic reports.
  • Task Management: Tracks investigation pipelines with Claude Native Tasks.
  • Frontend Verification: Visual verification of frontend implementations.

Quick Start

Use the ck:debug skill to systematically debug a code issue by following the systematic debugging framework.

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?▼

Systematic debugging is a four-phase framework that enforces root cause investigation before applying fixes. Root cause analysis traces bugs backward through the call stack to find the original trigger, ensuring the underlying issue is resolved rather than just treating symptoms.

How do I debug complex software issues using a systematic framework?▼

Debug complex software issues by following a four-phase systematic debugging framework: investigate the root cause, trace the bug backward through the call stack, apply fixes, and verify completion with fresh evidence to ensure the issue is structurally eliminated.

How do I diagnose system failures using CI/CD pipeline and log analysis?▼

Diagnose system failures by collecting and analyzing CI/CD pipelines and application logs. This investigation methodology follows a structured five-step process to identify the original trigger of system-level issues and validate data at every layer.

Can I identify performance bottlenecks and analyze query performance with this debugging approach?▼

Performance diagnostics are supported by this debugging approach to identify bottlenecks and analyze query performance. It integrates systematic investigation with performance tracing to isolate the root cause of system slowdowns and generate structured diagnostic reports.

Does this systematic debugging framework require specific scripts or debugging tools?▼

This systematic debugging framework requires Python scripts and various debugging tools to automate system investigation. Dependencies include shell scripts for finding polluters and JavaScript scripts for frontend visual verification and console interaction.

How do I verify frontend implementations during system debugging?▼

Verify frontend implementations during system debugging using visual verification scripts that capture screenshots and console outputs. This ensures frontend bugs are visually confirmed and validated against defense-in-depth protocols before completion.

Related Skills

Explore More Software Engineering Skills→
alexfalkowskialexfalkowski
2

diagnose-issue

Aggregate CircleCI, Kubernetes, and monitoring data to diagnose pipeline and deployment failures.

Community
Advanced
kirich1409kirich1409
23

debug

Investigate software bugs through a three-phase workflow and generate diagnostic debug reports.

Community
Advanced
drsapaevdrsapaev
2

webapp-testing

Test local web applications with Playwright Python scripts.

Community
Intermediate
juliuss1907juliuss1907

systematic-debugging

Automate root cause analysis and systematic debugging across four investigation phases.

Community
Advanced