skills.rest
duy-tung
duy-tungCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ck:debug

Debug software issues through systematic root cause analysis and verification.

Updated Jun 14, 2026
Search Tags:#code review#debugging#CI/CD#root cause analysis#systematic debugging#performance diagnostics
One-click install
npx skills add https://github.com/duy-tung/claude-code-setup --skill ck-debug-duy-tung
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:debug
Source: https://github.com/duy-tung/claude-code-setup/tree/main/claude/skills/ck-debug
Command: npx skills add https://github.com/duy-tung/claude-code-setup --skill ck-debug-duy-tung

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires psql, gh, npm, node, jest, playwright, cypress, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill solves the problem of inefficient debugging and root cause analysis, providing a systematic approach to resolve bugs, test failures, and unexpected behavior in software development.

Core Features & Use Cases

  • Systematic Debugging: A four-phase framework for debugging, including root cause investigation, pattern analysis, hypothesis testing, and implementation.
  • Root Cause Tracing: Traces bugs backward through the call stack to find the original trigger.
  • Defense-in-Depth: Validates at every layer data passes through to make bugs impossible.
  • Verification: Ensures no completion claims without fresh verification evidence.
  • Investigation Methodology: A five-step structured investigation for system-level issues.
  • Log & CI/CD Analysis: Collects and analyzes logs from servers and CI/CD pipelines.
  • Performance Diagnostics: Identifies bottlenecks and analyzes query performance.
  • Reporting Standards: Provides structured diagnostic reports.
  • Task Management: Tracks investigation pipelines via Claude Native Tasks.
  • Frontend Verification: Visual verification of frontend implementations.
  • Use Case: For a developer facing a performance degradation in a web application, this Skill can be used to systematically debug the issue, trace the root cause, and verify the fix.

Quick Start

Use the ck:debug skill to investigate a performance issue in your web application.

Frequently Asked Questions about ck:debug

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

FAQPage Schema
What is systematic debugging for root cause analysis in software engineering?▼

Systematic debugging uses a four-phase framework for root cause investigation, pattern analysis, hypothesis testing, and implementation to resolve bugs, test failures, and unexpected software behavior.

How do I trace the root cause of a performance issue in my web application?▼

Trace performance issues by collecting logs, analyzing CI/CD pipelines, identifying bottlenecks, and tracing bugs backward through the call stack to find the original trigger.

Can I use Playwright and Cypress for frontend debugging and visual verification?▼

Yes, you can use Playwright and Cypress to perform frontend debugging and visual verification of frontend implementations to ensure fixes work correctly.

Does this debugging framework work with Jest for test failure analysis?▼

Yes, the debugging framework works with Jest to analyze test failures, validate data passing through layers using defense-in-depth, and verify fixes with fresh evidence.

What is the best way to investigate system-level issues and server logs?▼

The best way to investigate system-level issues is using a five-step structured investigation methodology to collect and analyze logs from servers and CI/CD pipelines.

How do I ensure no completion claims are made without verification evidence?▼

Ensure no completion claims without verification by using defense-in-depth validation at every layer data passes through and requiring fresh verification evidence before completion.

Related Skills

Explore More Software Engineering Skills→
balamurubalamuru

prerequisites-checker

Verify external CLI tools and credentials before project setup.

Community
Intermediate
jangtrinhjangtrinh

ck:debug

Trace symptoms to root causes before applying fixes.

Community
Advanced
htooayelwinicthtooayelwinict

testing

Automate TDD workflows across Pest, Vitest, and Playwright test layers.

Community
Advanced
NickCrewNickCrew
29

python-performance-optimization

Profile Python code with cProfile and line_profiler to optimize performance.

Community
Advanced