Description
ce-debug is a diagnosis loop for bugs and failing or slow behavior. It finds the root cause of a failure, and then, when you choose, fixes it using test-first discipline. The skill is complete when the causal chain from the trigger to the symptom is stated without gaps and backed by file and line evidence, and either a verified fix has been handed off or a diagnosis-only summary has been delivered. It is designed not to persist forever: it escalates when two or three hypotheses have been tried without confirmation, or after three failed fix attempts. Its mode and blocking-question rules keep it from guessing at what you want. It is triggered when you ask to debug or fix failing or slow behavior. The skill is part of the compound-engineering plugin by Every and is listed on skills.sh as free.…
Highlights
- Finds the root cause of bugs and slow behavior
- Test-first fixes when you choose to fix
- Causal chain backed by file and line evidence
- Escalates after exhausting hypotheses or fix attempts
Ratings & Reviews
No ratings yet
Be the first to rate ce-debug.
People also visit
test-driven-development
Drives development with tests using the red-green-refactor loop
ce-debug FAQ
What does ce-debug produce?
A root-cause diagnosis with evidence, and either a verified fix or a diagnosis-only summary.
Does it fix the bug automatically?
It fixes when you choose to. Otherwise it delivers the diagnosis.
When does it stop?
It escalates after two or three hypotheses fail to be confirmed, or three failed fix attempts.
How do I install it?
Run npx skills add https://github.com/everyinc/compound-engineering-plugin --skill ce-debug in your terminal.
Is it free?
The listing shows the skill as free.
What are the best ce-debug alternatives?
Popular alternatives to ce-debug include orch-fix-defect, debugging-and-error-recovery and test-driven-development. See all ce-debug alternatives