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.
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
- List your label taxonomy with one-line meanings
- Trigger a GitHub Action on new issues and PRs
- Ask Jev a Choice question per label group
- Add labels above the confidence bar, never remove existing ones
- Maintainers fix mislabels and review the taxonomy quarterly
Tools
- Jev (TypeSafe AI)
- GitHub Actions
- OpenRouter
Risks and guardrails
- Sparse issue text gives weak labels
- Taxonomy drift if labels are added without descriptions
- Bots that label too much get ignored
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- Jev PR Labeler by Jeremy Huang on Made with Jev: madewithjev.com/builds/jev-pr-labeler
- Jev PR Labeler: original post or repo by Jeremy Huang: github.com/1jehuang/jev-pr-labeler
- DeciLabel by EvanProgramming on Made with Jev: madewithjev.com/builds/decilabel
- DeciLabel: original post or repo by EvanProgramming: github.com/EvanProgramming/decilabel
- jev-review-action by wang2 on Made with Jev: madewithjev.com/builds/jev-review-action
- jev-review-action: original post or repo by wang2: github.com/fatwang2/jev-review-action
- GitHub repo smart-labeler by hkurma: github.com/hkurma/smart-labeler
- OpenRouter (official page): openrouter.ai (checked 2026-11-09)