jev-triagelisted
Install: claude install-skill WanLanglin/jev-skills
# jev-triage
The value here is not the labels — you can label things yourself. The value is
that the obvious cases cost nothing, so you only spend real reasoning where it
is needed. **Read the confidence caveat below before you trust the split.**
## Use it
```bash
python3 "$CLAUDE_SKILL_DIR/../../scripts/triage.py" \
--question "Is this review finding a real defect?" \
--label real="a genuine bug that would cause wrong behaviour or a crash" \
--label style="naming, formatting, or preference only" \
--label wrong="the finding misreads the code and is not a defect" \
--escalate-below 0.9 \
--items findings.txt
```
Multi-line items (stack traces, diff hunks, findings with code):
```bash
python3 .../triage.py --sep $'\n---\n' --items hunks.txt \
--question "How risky is applying this hunk automatically?" \
--label safe="isolated, easy to revert, well covered by tests" \
--label review="touches shared state or public API" \
--label danger="security, auth, migrations, or data loss"
```
Add shared background once with `--context` — it is billed once for the whole
batch, not per item, so be generous with it.
## The part that matters
Output splits into decided buckets and an **escalate** list. The escalate list
is the whole point: those are the items where a confident-looking answer would
have been wrong. Send exactly those to a subagent or handle them yourself, and
accept the rest.
`--escalate-below` defaults to **`0.90`**, and that number is measured, no