skills.rest
MinhQuyen274
MinhQuyen274COMMUNITY
Explore all skills by this author →
GitHub

ck:debug

Enforce root-cause investigation before fixing code, test, or CI/CD failures.

Updated Aug 27, 2026
Search Tags:#debugging#root cause analysis#verification#log analysis#database diagnostics#performance diagnostics#CI/CD troubleshooting
One-click install
npx skills add https://github.com/MinhQuyen274/smartify --skill ck-debug-minhquyen274
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:debug
Source: https://github.com/MinhQuyen274/smartify/tree/main/Frontend_PROJECT_Figma/.opencode/skills/debug
Command: npx skills add https://github.com/MinhQuyen274/smartify --skill ck-debug-minhquyen274

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Eliminates wasted effort from guess-based debugging by enforcing systematic root-cause investigation before any code changes or claims of success.

Core Features & Use Cases

  • Systematic debugging workflow: Root Cause Investigation → Pattern Analysis → Hypothesis Testing → Implementation.
  • Root cause tracing through call stacks: Trace backward to the original trigger, not the symptom.
  • Defense-in-depth validation: Add validation and instrumentation at multiple layers to make bugs structurally harder to reintroduce.
  • Verification-first completion: Requires fresh evidence (tests/build/outputs) before declaring the issue resolved.
  • System investigation for CI/CD, logs, databases, and performance: Supports multi-component incident handling with structured evidence gathering and reporting.

Quick Start

Run the debug skill for a failing test or unexpected behavior and follow the phases to identify and validate the root cause before applying a fix.

Frequently Asked Questions about ck:debug

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

FAQPage Schema
How do I find the root cause of a failing test instead of just patching the symptom?▼

To find the root cause of a failing test, trace backward through the call stack to the original trigger rather than the symptom, then gather evidence from logs and CI outputs before applying any code fixes.

What is the best way to debug CI/CD pipeline failures and server incidents systematically?▼

The best way to debug CI/CD failures and server incidents is structured evidence gathering across components, enforcing layered validation and backward call-stack tracing to identify the original trigger before making changes.

How do I verify a bug fix is actually resolved before claiming completion?▼

To verify a bug fix is resolved, you must produce fresh evidence such as passing tests, successful builds, or corrected outputs, blocking any completion claims until this proof is validated.

Can I use systematic debugging for database and performance anomalies?▼

Yes, systematic debugging applies to database and performance anomalies by requiring multi-component system investigation, structured log analysis, and diagnostics to trace the root cause before fixes.

Why does guess-based debugging waste effort and how does root cause analysis prevent it?▼

Guess-based debugging wastes effort by treating symptoms; root cause analysis prevents this by enforcing a workflow of investigation, pattern analysis, hypothesis testing, and implementation to eliminate thrash.

Related Skills

Explore More Software Engineering Skills→
quanganh208quanganh208

ck:debug

Debug software through a four-phase root cause investigation workflow.

Community
Advanced
cookercooker
66

verification-before-completion

Verify command outputs before declaring task completion with fresh evidence.

Community
Basic
Thanh-aperoThanh-apero
1

ck:debug

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

Community
Advanced
TimHL5TimHL5

canary

Monitor post-deploy web apps for console errors, performance metrics, and page failures.

Community
Advanced