skills.rest
xotong
xotongCOMMUNITY
Explore all skills by this author →
GitHub

ce-debug

Trace root causes of bugs through phased triage, investigation, and fix workflows.

2|Updated May 8, 2026
Search Tags:#debugging#investigation#troubleshooting#evidence#phases#root-cause#engineering-process
One-click install
npx skills add https://github.com/xotong/claude-marketplace --skill ce-debug-xotong
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce-debug
Source: https://github.com/xotong/claude-marketplace/tree/main/plugins/compound-engineering/skills/ce-debug
Command: npx skills add https://github.com/xotong/claude-marketplace --skill ce-debug-xotong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically identify root causes of bugs, trace the full causal chain, and provide actionable fixes or handoffs. This skill enforces a disciplined debugging approach to reduce guesswork and improve reliability.

Core Features & Use Cases

  • Structured phases: triage, investigate, root cause, fix, and handoff to ensure complete analysis.
  • Evidence-backed reasoning: require observations, data, and predictions to validate hypotheses.
  • Safe change management: emphasize test-first fixes and minimal changes with rollback considerations.
  • Use Case: when a user says "debug this" or a stack trace is pasted, ce-debug guides the process end-to-end.

Quick Start

Describe the bug concisely and paste the relevant stack trace to kick off the phased debugging workflow.

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

Root cause debugging requires a phased process: triage, investigate, root cause, fix, and handoff. You trace the full causal chain by gathering evidence, validating hypotheses with observations, and enforcing test coverage for any proposed fixes.

What is the best way to systematically debug a code defect from a stack trace?▼

Systematically debugging a code defect involves pasting the stack trace and describing the bug to initiate a structured investigation. This enforces evidence-backed reasoning, requiring data and predictions to validate hypotheses before applying safe, minimal changes.

How do I troubleshoot a reproducible test failure across multiple environments?▼

Troubleshooting test failures across environments uses a disciplined debugging approach to reduce guesswork. It applies evidence gathering and causal-chain justification to trace the root cause, ensuring fixes include instrumentation and test coverage.

When should I use a phased debugging process for software engineering investigation?▼

A phased debugging process is needed whenever you face code defects, test failures, or reproducible issue reports. It enforces structured phases—triage, investigate, root cause, fix, and handoff—to ensure complete analysis and safe change management.

Can I apply systematic debugging to issue reports across different platforms?▼

Yes, systematic debugging applies to code defects and reproducible issue reports across multiple platforms and environments. It enforces strict discipline against symptom fixes by requiring causal-chain justification and instrumentation for any proposed fixes.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

debugging-assistant

Diagnose software bugs from stack traces and error logs.

Community
Advanced
sgcarstrendssgcarstrends
21

coverage-analysis

Analyze Vitest coverage across monorepo packages and generate reports.

Official
Advanced
xxihxxih
1

systematic-debugging

Identify root causes of bugs through a four-stage systematic process.

Community
Intermediate
kay6198835kay6198835

bug-report

Convert user descriptions into structured bug reports with reproduction steps.

Community
Advanced