jevbooks

← All projects

jev-issue-triage

elcann7/jev-issue-triage

Label and prioritize GitHub issues with Jev; code decides.

Automated README summary

Automatically summarized from the README on 3 Nov 2026; not a run by jevbooks. Run instructions and author-reported outcomes still need verification.

What it is

A GitHub Action for maintainers of busy repositories that reads each new issue, labels it, and assigns a priority tier. An optional local dashboard shows the backlog grouped by urgency.

How it uses Jev

Jev answers nine typed questions per issue (is_bug, is_feature_request, is_question, is_docs, has_repro, describes_vulnerability, leaks_secret, is_spam, and a four-level severity score) in one request. Probabilities become yes/no/unsure via thresholds, and a fixed decision table in src/decide.mjs turns them into labels and a tier.

Primitives:choicescore

Technique worth stealing

Keep the model to small per-question judgments and let a readable, tested decision table map probabilities to labels.

Try it

Add the workflow with dry_run: "true", open a test issue, and read the job summary.

View on GitHub

Start using Jev: API key and your first request →

Model judgments from README excerpts

Project signals use repository metadata, an existing summary and the first 700 README characters, not the full project. “Not found” means not detected in that material; it does not establish absence. These are the original judgments with recorded models and dates, not source audits or run results.

Models & evaluation dates

Inclusion gate
jev-1.14.0
Project signals
jev-1.14.0
Category
jev-1.14.0
Pattern tags
jev-1.14.0

Evidence

These signals use repository metadata, an existing summary and at most 700 cleaned README characters. ≥ 0.60 means reported in that excerpt; ≤ 0.40 means not found there. The middle band is inconclusive. None is a source-code audit or a test result. The runnable-tool question excludes research experiments; the recommendation question asks for a learning shortlist, not a quality verdict.

  • Jev is core to the projectFound in material0.89
  • Shows a System One patternunclear0.45
  • Describes handling uncertaintynot found in the excerpt0.04
  • Reports measured numbersnot found in the excerpt0.02
  • Is a runnable toolFound in material0.94
  • Top-10 learning shortlist signalnot found in the excerpt0.22
  • Is a replica of the modelnot found in the excerpt0.02
  • Solves a common problem (0–2)score on a 0–2 scale1.59 / 2
  • About JevFound in material0.99
Signals
Jev is core to the project0.89Shows a System One pattern0.45Describes handling uncertainty0.04Reports measured numbers0.02Is a runnable tool0.94Top-10 learning shortlist signal0.22Is a replica of the model0.0200.51Solves a common problem (0–2)1.59 / 2012

no-judgment band (0.40–0.60)

Design patterns
Questionnaire0.98Traffic light0.98Grey zone0.94Fail open, fail closed0.89Scorecard0.76Thermostat0.57Question bank0.54Prefetch0.33Funnel0.26Check-up0.2100.51

no-judgment band (0.40–0.60)

The Jev model and date for each judgment stage are listed above. Card written by DeepSeek V4.1 Flash from the README on 3 Nov 2026.