Investigate Before Editing
Diagnoses unclear failures with ranked hypotheses before any code is changed.
Install
npx skills add JuliusBrussee/caveman --skill investigate-first -g -a claude-code -y- Repository
- JuliusBrussee/caveman117k
- Category
- Engineering
- Updated
- 3d ago
- License
- Apache-2.0
- Context cost
- Lightabout 118 tokens
- Runs scripts
- No, instructions only
What it does
Diagnose ambiguous failures before editing. Use for unknown causes, intermittent behavior, performance regressions, or investigations needing evidence-ranked hypotheses.
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.
