skills.rest
yxc023
yxc023COMMUNITY
Explore all skills by this author →
WebsiteGitHub

ce-debug

Trace bugs from trigger to symptom and produce a root-cause plan.

Updated Apr 22, 2026
Search Tags:#testing#debugging#reproducibility#issue-tracking#systematic-troubleshooting#root-cause-analysis#causal-chain
One-click install
npx skills add https://github.com/yxc023/agent-config-studio --skill ce-debug-yxc023
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce-debug
Source: https://github.com/yxc023/agent-config-studio/tree/main/.opencode/skills/ce-debug
Command: npx skills add https://github.com/yxc023/agent-config-studio --skill ce-debug-yxc023

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ce-debug helps teams systematically identify root causes of bugs and craft reliable fixes, reducing time spent chasing symptoms.

Core Features & Use Cases

  • Structured debugging workflow follows a five-phase approach (Triage, Investigate, Root Cause, Fix, Close) to guide problem solving from symptom to solution.
  • Evidence-driven analysis emphasizes reproducible steps, hypotheses, and tests to validate fixes and avoid symptom fixes.
  • Cross-tool applicability supports debugging across error messages, stack traces, test failures, and issue trackers.

Quick Start

Describe a bug scenario and let ce-debug guide you through triage, investigation, root-cause, fix, and close.

Frequently Asked Questions about ce-debug

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

FAQPage Schema
How do I find the root cause of a bug instead of just fixing the symptom?▼

To find the root cause of a bug, trace the full causal chain from trigger to symptom using a structured debugging workflow. This evidence-driven approach emphasizes reproducible steps and hypotheses to validate fixes and avoid treating symptoms.

What is the best way to debug failing tests and stack traces systematically?▼

The best way to debug failing tests and stack traces is applying a phased debugging process: Triage, Investigate, Root Cause, Fix, and Close. This enforces evidence-driven analysis to reliably resolve test failures and trace errors.

How do I start troubleshooting an issue tracker bug report?▼

Start troubleshooting an issue tracker bug report by describing the bug scenario to initiate the triage phase. This guides you through investigation and root-cause identification using established references and reproducible steps.

Can I use a systematic debugging workflow for error messages and issue trackers?▼

Yes, you can use a systematic debugging workflow across error messages, failing tests, issue trackers, and stack traces. It applies cross-tool applicability to guide problem solving from symptom to reliable solution.

Why should I use a structured debugging process instead of ad-hoc troubleshooting?▼

You should use a structured debugging process instead of ad-hoc troubleshooting to reduce time spent chasing symptoms. It enforces a five-phase approach to validate fixes with evidence and produce a reliable root-cause plan.

What are the limitations of symptom-driven debugging for complex system failures?▼

Symptom-driven debugging limitations include failing to identify the actual trigger and wasting time on incomplete fixes. A structured, root-cause analysis approach avoids this by tracing the full causal chain to validate reliable solutions.

Related Skills

Explore More Software Engineering Skills→
wtthorntonwtthornton
4

debugger

Diagnose software bugs by analyzing error messages and stack traces.

Community
Advanced
MissTullyMissTully

gstack-openclaw-investigate

Diagnose software issues through a phase-driven root-cause analysis workflow.

Community
Advanced
rnaarlarnaarla

diagnose

Diagnose hard bugs through reproducible loops and structured hypotheses.

Community
Advanced
StrategicMilkStrategicMilk

Monitoring and Alerting

Detect operational anomalies in system metrics using statistical process control.

Community
Advanced