Labels
Tigent works best when labels are descriptive, semantic, and clearly separated from workflow-only markers that belong in the blocklist.
Write Descriptions That Teach The Model
Tigent reads label descriptions from github every time it triages. better descriptions mean better classification without bloating the prompt.
something is not working as expected in the product or sdk.
new functionality, requested capability, or meaningful enhancement.
changes or gaps in guides, api docs, examples, or reference material.
Semantic Labels Versus Workflow Labels
Semantic
labels like bug, support, documentation, or provider/openai can usually be inferred from content.
Workflow
labels like backport, major, or good first issue usually depend on release process or maintainer judgment.
Best Practice
blocklist.Label Design Tips
use consistent nouns and verbs across descriptions so related labels cluster naturally.
avoid vague descriptions like misc or general unless you really want a catch-all label.
if two labels overlap heavily, clarify the boundary in the descriptions or in the prompt.