Issue triage & routing
On the schedule you choose, the agent classifies and dedupes incoming issues, verifies the actionable ones, proposes labels and routing under explicit rules, and drafts a triage summary for you to approve before anything is applied.
What it installs
Agents 1
-
Triage Agent
Triages incoming issues against a state machine and drafts a triage summary.
Workflows 1
-
Triage issues
Classify and dedupe, verify the actionable ones, then draft a triage summary for approval.
Goals 1
-
Issues triaged daily
Incoming issues are classified, deduped, verified, and labelled without backlog.
Skills 3
-
triage-frontend-issues
Archive non-actionable noise from the issue queue safely: archive-only, always with a stated reason, weigh stack-frame and title signals, and when in doubt skip and flag for a human. Adapted from getsentry/skills/triage-frontend-issues.
-
github-triage
Move issues and external PRs through a triage state machine: gather context, check for duplicates and prior rejection, recommend a category and state, verify the claim, and write a durable, agent-ready brief. Adapted from mattpocock/skills/triage.
-
triage-issue
Break a thick report into independently-grabbable issues using thin vertical slices, each with a durable description, acceptance criteria, and honest blocking order. Adapted from mattpocock/skills/to-issues.
Schedules 1
-
Triage issues
Triages incoming issues on the schedule you choose.
Requirements
What this template expects to do its job. Task Machine does not verify these — you decide whether your setup is ready.
- Connected repository — Needs a connected code repository so the agent can read the incoming issue queue, check the codebase for context and duplicates, and propose label updates.
Get started
Install Issue triage & routing and run it with approvals.
Join the waitlist and we will send early access when the first private beta spots open.
Private beta. We invite teams in batches and never share your email.