Root cause
Use when Codex needs to analyze a failing JUnit 5 test run, identify the most likely root cause, and produce a developer-focused diagnosis with concrete next fixes.From its SKILL.md
npx -y skills add jovd83/junit5-skill --skill root_causeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, 156 tokens by cl100k_base, as published. Nobody here has run it
JUnit 5 Root Cause Analysis
1. Capture the Failure
- Capture the failing class, method, stack trace, and environment details.
- Reproduce the failure as narrowly as possible.
- Separate symptom from suspected cause.
2. Classify the Failure
- Check for assertion mismatch.
- Check for fixture leakage or ordering issues.
- Check for environment mismatch.
- Check for timing, randomness, file system, locale, or time zone issues.
- Check for a real production bug.
3. Report the Diagnosis
- State the most likely root cause.
- State the evidence supporting that conclusion.
- State the smallest safe next fix.
- State any remaining uncertainty explicitly.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.