ce-debug

Trace bug causal chains from trigger to symptom and guide corrective actions.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/DieStok/ridder_lab_retreat_ai_hackathon_2026 --skill ce-debug-diestok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce-debug
Source: https://github.com/DieStok/ridder_lab_retreat_ai_hackathon_2026/tree/main/.agents/skills/compound-engineering/skills/ce-debug
Command: npx skills add https://github.com/DieStok/ridder_lab_retreat_ai_hackathon_2026 --skill ce-debug-diestok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Find root causes in bugs systematically by tracing the full causal chain from trigger to symptom and guiding corrective actions.

Core Features & Use Cases

  • Phase-guided debugging workflow (Triage, Investigate, Root Cause, Fix, Handoff) to reproduce and resolve bugs with evidence.
  • Structured hypotheses, predictions, and smart escalation to prevent symptom-focused fixes.
  • Defense-in-depth guidance to ensure robust fixes across multiple layers.

Quick Start

Describe the bug and provide any error messages or reproduction steps, then start Phase 1: Investigate to reproduce and trace the issue.

Frequently Asked Questions about ce-debug

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

FAQPage Schema
How do I systematically debug code when stack traces are incomplete?▼

Systematically debug incomplete stack traces by tracing the full causal chain from trigger to symptom. This structured investigation approach uses evidence-based hypotheses and phase-guided workflows to reproduce and resolve bugs.

What is the best way to find a root cause in a complex codebase?▼

Find root causes in complex codebases by validating structured hypotheses against evidence through a multi-phase workflow. Triage, investigate, and isolate the causal chain to prevent symptom-focused fixes and guide corrective actions.

Why do my bug fixes only address symptoms instead of the root cause?▼

Symptom-focused fixes often occur when the causal chain is untraced. Structured debugging enforces evidence-based hypotheses and root-cause analysis across a phase-guided workflow, ensuring corrective actions target the actual trigger.

How do I structure a debugging workflow for issue trackers in complex codebases?▼

Structure a debugging workflow across issue trackers using phases: Triage, Investigate, Root Cause, Fix, and Handoff. This workflow reproduces bugs with evidence, validates predictions, and guides defense-in-depth fixes across multiple layers.

Can I use structured hypotheses to reproduce and resolve bugs across complex codebases?▼

Yes, structured hypotheses guide reproduction and resolution across complex codebases by validating predictions and tracing the full causal chain. Smart escalation prevents incomplete fixes by ensuring evidence-based root-cause isolation before applying fixes.

When should I not use a symptom-focused approach to fix bugs?▼

Avoid symptom-focused approaches when stack traces are incomplete or hypotheses need structured validation. Use root-cause analysis with defense-in-depth guidance to ensure robust fixes across multiple layers instead of patching surface symptoms.