ck:debug

Trace root causes across code, tests, CI/CD logs, and databases.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/hidonguyen/trade-ops --skill ck-debug-hidonguyen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:debug
Source: https://github.com/hidonguyen/trade-ops/tree/main/.opencode/skills/ck-debug
Command: npx skills add https://github.com/hidonguyen/trade-ops --skill ck-debug-hidonguyen

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Systematically investigate and resolve software and system failures by tracing root causes before applying fixes, preventing wasted effort and regressions.

Core Features & Use Cases

  • Systematic four-phase debugging workflow: investigation, pattern analysis, hypothesis testing, implementation.
  • Root-cause tracing through call stacks and test bisection, including a bisection script to find polluting tests.
  • Defense-in-depth validation across entry points, business logic, environment guards, and debug instrumentation.
  • Log and CI/CD analysis, performance diagnostics, database forensics, structured investigation reports, and task-managed investigation pipelines.
  • Use cases: flaky tests and test pollution, CI failures, server 500s, slow queries, multi-service incidents, and frontend visual regressions.

Quick Start

Ask ck:debug to investigate "500 errors on /api/orders" providing stack traces, CI logs, recent commits, and reproduction steps and request root cause, mitigation, and verification steps.

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 flaky tests and test pollution in my CI pipeline?

Find the root cause of flaky tests by applying test bisection scripts to isolate polluting tests, then trace failures across call stacks and structured CI logs. This systematic investigation prevents wasted effort on symptomatic fixes.

What is the best way to diagnose server 500 errors across multi-service incidents?

Diagnose multi-service incidents by correlating evidence across code, structured logs, and database forensics. This approach applies hypothesis testing to verify root causes before applying fixes, ensuring reliable multi-service incident resolution.

How do I systematically debug performance regressions and slow database queries?

Debug performance regressions through structured log analysis and database diagnostics to identify slow queries. The workflow applies defense-in-depth validation to verify mitigation steps and prevent future performance degradation.

Can I use test bisection to identify polluting tests causing CI pipeline failures?

Yes, you can use test bisection scripts to identify polluting tests causing CI pipeline failures. The investigation workflow traces root causes through call stacks and CI logs to verify fixes reliably and prevent regressions.

Why should I use a systematic debugging workflow instead of directly patching code?

A systematic debugging workflow traces root causes before applying fixes, preventing wasted effort and regressions. It implements defense-in-depth validation across entry points, business logic, and environment guards to verify fixes reliably.

Does this debugging approach work for frontend visual regressions and CI failures?

Yes, this debugging approach works for frontend visual regressions and CI failures by applying pattern analysis and hypothesis testing. It traces root causes across code, tests, and structured logs to verify mitigation steps.