Agents Lookup

Use cases / Decision models (Jev)

Label GitHub issues and pull requests from a fixed taxonomy

Have Jev pick type, area and size labels for each new issue or PR from your taxonomy, adding only labels the text supports.

DifficultyBeginner
Setup time1-2 hours
CategoryDecision models (Jev)

The use case

Open-source maintainers and product teams spend time labelling issues and pull requests so the right people see them. These actions send the title, body and changed files to Jev with Choice questions over the repository's own labels, such as kind, component, OS and scope, where scope means scope rather than lines changed. Only labels above a confidence bar get added, and existing labels are never removed. Maintainers correct wrong labels, and those corrections are a good set to test any change to the questions.

Example workflow

  1. List your label taxonomy with one-line meanings
  2. Trigger a GitHub Action on new issues and PRs
  3. Ask Jev a Choice question per label group
  4. Add labels above the confidence bar, never remove existing ones
  5. Maintainers fix mislabels and review the taxonomy quarterly

Tools

Risks and guardrails

Sources

Written by Agents Lookup. Credits and official pages for the tools this use case names: