ce-debug
Diagnosis loop for bugs and failing behavior. Use for errors, stack traces, regressions, failed tests, issue-tracker bugs, stuck investigations after failed fixes, or asks to debug/fix a bug.
Install
Install this Claude and Codex skill with the command below. The command stays visible even when copy support is unavailable.
git clone https://github.com/EveryInc/compound-engineering-plugin /tmp/compound-engineering-plugin && ln -s /tmp/compound-engineering-plugin/skills/ce-debug ~/.claude/skills/ce-debugFrom README
Debug and Fix Find root causes, then fix them. This skill investigates bugs systematically — tracing the full causal chain before proposing a fix — and optionally implements the fix with test-first discipline. The bug description is the input this skill was invoked with — the failure to diagnose, present in the current prompt or conversation, whether the user provided it directly or a calling skill passed it (e.g. ce-babysit-pr / lfg in mode:pipeline, which pass the failing jobs and log tails as the argument). It may be a description of the failure, a mode: token, or an issue reference (#123, org/repo#123, or an issue URL). The rest of this skill refers to it as ; if nothing was provided, treat as blank. Mode Default is interactive — investigate, then use the Phase 2 fix-choice gate and the Phase 4 handoff prompt as written below. mode:pipeline (set by an orchestrator such as ce-babysit-pr or lfg): run fully non-interactively. Strip the mode:pipeline token from before parsing.