ce-debug
Diagnosis loop for bugs and failing or slow behaviour.
- Kind
- Skill
- Works with
- Claude Code, Codex, Cursor, Any agent
- Source
- EveryInc/compound-engineering-plugin @ 786ac0194183
- Path
- skills/ce-debug/SKILL.md
- License
- MIT
- Jobs
- Debugging
InstallInstall it from a plugin marketplace.
/plugin install compound-engineering
# Debug and Fix Find the root cause of a failure, then — when the user chooses to — fix it with test-first discipline. **Done when:** the causal chain from trigger to symptom is stated with no gaps and file:line evidence, and either a verified fix has been handed off (PR, commit, or the user's chosen stop) or a diagnosis-only summary has been delivered. **Escalate rather than persist:** 2-3 hypotheses exhausted without confirmation, or 3 failed fix attempts, means diagnose *why* instead of trying again — that is the smart escalation `references/investigate.md` describes. One hypothesis, one change at a time; changing several to see what helps is shotgun debugging. `<bug_description>` is whatever this skill was invoked with — a failure description, a `mode:` token, or an issue reference (`#123`, `org/repo#123`, an issue URL) — from the user or from a calling skill (`ce-babysit-pr` / `lfg` in `mode:pipeline` pass the failing jobs and log tails; `lfg`'s defect route passes `mode:return-to-caller` and the user's own reference). Blank if nothing was provided. ## Mode Default is **interactive**: investigate, run the Phase 2 fix-choice gate, then the Phase 4 handoff. …