investigate-first
This skill helps developers diagnose ambiguous failures before editing code. It guides you to separate symptoms from root causes, trace inputs and state transitions, and rank hypotheses by evidence. By preventing untested edits, it cuts mean time to root-cause identification and reduces regression risk.
npx skills add https://github.com/juliusbrussee/caveman --skill investigate-firstBefore / After Comparison
1 组Developers facing intermittent failures often change code based on intuition, taking an average of 4 hours to locate the root cause and risking new regressions.
This skill guides evidence-based investigation, cutting mean time to root cause to 30 minutes and reducing unintended modifications.
Investigate first
Gather evidence before changing product code.
- Separate observed symptom from inferred cause.
- Trace inputs, state transitions, ownership boundaries, and failure output.
- Rank hypotheses by evidence and cheap falsification value.
- Do not edit until one credible mechanism explains evidence.
- Stop exploration when evidence is sufficient to name cause or exact blocker.
Report cause and proof. Make no fix unless task authorizes implementation.
User Reviews (0)
Write a Review
No reviews yet
Statistics
User Rating
Rate this Skill