Issue Triage

issue-triage

GitHub issues labeled and triaged the moment they arrive.

v0.2.4Remixable<1k installs1.6M tokens usedNo reviews yet

Remix creates your own version in chat. The original stays unchanged.

Daily token usage

Last 30 days

Today

191.8K

Issue Triage

Keep your GitHub issues sorted automatically — the right type, priority, and area labels, applied the moment an issue lands.

What it does

Issue Triage reads each new or edited GitHub issue, classifies it, and applies labels directly on GitHub. It combines your repository's own labels with a built-in issue-type taxonomy, so type and priority are consistent everywhere while area/component labels stay true to how your project already organizes work. Every triage is recorded with its reasoning, so you can see not just what was labeled, but why.

Features

  • Automatic labeling — turn on auto-triage for a repo and new, edited, or reopened issues get labeled without you lifting a finger.
  • Type, priority, area, and flags — one type and one priority per issue, area labels drawn only from your existing labels, plus needs-info / needs-triage flags when an issue is thin or ambiguous.
  • Batch and one-off triage — sort a whole backlog of open issues at once, or triage a single issue by URL from the dashboard.
  • Your rules — enable or disable each dimension per repo and add custom triage guidance the classifier will follow.
  • Full activity log — a feed of every triage with the applied labels, classification, and reasoning.

When to use it

Reach for Issue Triage when a repository gets more issues than you can hand-sort, when you want consistent labels across a team, or when you're staring down a backlog of unlabeled issues and want them organized in one pass.


GitHub must be connected via Rome's managed gh CLI. No repository webhook is registered until you enable auto-triage for a repo.