jev-logscanlisted
Install: claude install-skill WanLanglin/jev-skills
# jev-logscan
A build just printed 17,000 lines and six of them explain the failure. Reading
all of it costs your context; scrolling for the error costs your turn.
## Use it
```bash
pytest -v 2>&1 | python3 "$CLAUDE_SKILL_DIR/../../scripts/logscan.py" \
--goal "find out which test failed and why"
```
```bash
python3 .../logscan.py --log build.log --goal "find out why the link step failed"
python3 .../logscan.py --log train.log --goal "find where loss became NaN" --budget 60
```
**`--goal` is the whole interface.** The ranking is conditioned on it, so ask
for what you actually want:
- `"why did this fail"` → errors, tracebacks, the failing assertion
- `"where did it get slow"` → timings and durations, not errors
- `"what configuration was used"` → the settings echoed at startup
- `"what ran out of memory"` → allocation and OOM lines
Same log, different lines out.
## Reading the output
Lines come back **in their original order**, with elided runs marked, because a
log read out of sequence is unusable. Original line numbers are preserved so you
can go back to the source. A `!` marks a line that matched an error shape
(traceback, `SyntaxError:`, `FAILED`, `panic:`) and was kept regardless of score.
If nothing in the log addresses your goal, it says so instead of padding the
output with the least-bad lines.
## How it decides
Logs are templated — a build prints `Compiling './x'...` seventeen thousand
times — so lines are collapsed to their shape first (paths, numbers