ce-debug

Guide structured root-cause analysis to identify and resolve software bugs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/xbpk3t/ce-codex --skill ce-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-debug
Source: https://github.com/xbpk3t/ce-codex/tree/main/skills/ce-debug
Command: npx skills add https://github.com/xbpk3t/ce-codex --skill ce-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systematically identify root causes of bugs and provide repeatable fixes through a formal debugging workflow.

Core Features & Use Cases

  • Structured investigation phases: triage, investigation, root-cause analysis, and optional fix/closure.
  • Guided best practices: references to anti-patterns and investigation techniques to avoid common debugging pitfalls.
  • Use Case: when you face intermittent failures or unclear error traces, this skill guides you from symptom to root cause and recommended remediation.

Quick Start

Describe a failing scenario or paste a stack trace to begin the investigation workflow.

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 and fix software bugs through root-cause analysis?

To debug and fix software bugs, follow a structured root-cause analysis workflow that moves through triage, evidence gathering, hypothesis formation, and test-first fixes to ensure robust remediation.

What is the best way to troubleshoot intermittent test failures when I only have an unclear error trace?

Troubleshooting intermittent test failures requires a phased investigation approach that gathers evidence from the unclear error trace, forms hypotheses, and enforces test-first fixes to verify the root cause.

Can I use a structured debugging workflow for issue-tracker reproductions across different codebases?

Yes, a structured debugging workflow is suitable for investigating issue-tracker reproductions across codebases, guiding you from symptom identification to root-cause analysis and final verification.

How do I start an investigation if I just paste a stack trace from a failing scenario?

Pasting a stack trace from a failing scenario initiates the investigation workflow, which systematically guides you through evidence gathering and root-cause analysis to resolve the bug.

What common debugging anti-patterns should I avoid when trying to identify a root cause?

When identifying a root cause, avoid common debugging anti-patterns by using guided best practices and investigation techniques that enforce evidence gathering and structured hypotheses instead of guesswork.

Does this debugging method include the actual code fix or just the investigation phases?

This debugging method includes optional fix and closure phases after triage, investigation, and root-cause analysis, ensuring that any code fix is test-first and verified for robust remediation.