Reference

Feedback

Mention @tigent in a comment to explain a decision, correct labels, update the blocklist, or teach a repo-specific rule in natural language.

Who Can Use Feedback

Trusted Authors Only

only repository owners, members, and collaborators can trigger feedback actions. comments from other users are ignored.

Explain Natural Message Patterns

Explain

ask why tigent chose labels and it will restate the decision with any blocked labels or memory it used.

Correct

tell tigent the current labels are wrong and what they should be instead.

Update Blocklist

tell tigent to leave specific workflow labels to humans and it can prepare a config change.

Example Comments

tigent.yml

@tigent why did you label this as a bug?
@tigent this should be support and ai/provider
@tigent remove documentation and add support
@tigent never apply backport automatically. update tigent.yml
@tigent leave major and minor to humans

How Learning Works

Trusted corrections are stored as repo memory. future triage retrieves the most relevant examples and uses them as precedent alongside the prompt and available labels.

Verification First

when tigent proposes a config change, it verifies that change against the issue or pr that triggered it. if verification fails, the learning pr becomes a draft instead of pretending the system improved.

When Tigent Asks For Clarification

If a maintainer says a decision is wrong but does not provide enough direction, tigent should ask a short follow-up rather than guessing. that keeps the learning loop high-signal.

Labels