Root cause
Rest Assured skill pack for designing, implementing, documenting, and reporting API tests in Java and CI workflows.
npx -y skills add jovd83/restassured-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
- 2 stars2 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.
What its author says it does
Copied from the file, not written here
Use when Codex needs to analyze failing Rest Assured API tests, identify the most likely root cause, and produce a developer-focused failure diagnosis.
SKILL.md
1.5 KB, as published. Nobody here has run it
Root Cause Analysis
1. Gather Evidence
- Capture the failing request and response.
- Capture the exact assertion failure.
- Capture environment details, auth details, and dependency behavior.
- Capture container or stub logs when relevant.
2. Identify The Failure Class
- Classify the failure as environment, auth, contract drift, test data, dependency outage, assertion bug, or application defect.
- State the most likely root cause first.
- State competing hypotheses only when evidence is incomplete.
3. Produce The Diagnosis
- State what failed.
- State why it most likely failed.
- State how to confirm it.
- State the recommended fix.
4. Troubleshooting
- Problem: The evidence is incomplete. Fix: State the gap and request the missing artifact explicitly.