When an issue is opened, classifies it (bug, feature request, question, docs, task), checks whether it has the information a maintainer needs to act (repro steps, expected vs actual, version, logs), assesses severity for bugs, applies labels, and posts a triage comment with routing. When a ticket system is connected, files actionable work as a ticket and links it back — checking first that one does not already exist.
- Identifier
issue-triage- Version
- 1.1.0
- Steps
- 3
- Triggers
- 1
- triage
- issues
- routing
- hygiene
- automated
When it runs
issue.opened- Settle delay
- 10s after the event
Only when all hold
- actor.username not in dependabot, dependabot[bot], renovate, renovate[bot], github-actions, github-actions[bot]
- actor.username not contains [bot]
The pipeline
The graph below is the one the workflow opens with in the builder — same steps, same layout, drawn on the same canvas. The run playing through it is a simulation; the branches and conditions are real.
- 01Issue Opened
triggerThe event that starts the run.
- 02Triage Issue
agent.runOne agent works the task with its toolkit.
- 03Publish Triage Report
report.publishPosts or updates a deduplicated report comment.
The agent
Issue Triager
- Base type
- Senior Developer
- Temperature
- 0.2
- Max iterations
- 15
- Tools
- 4
Tickets · 2
list_ticketsList Tickets · readcreate_ticketCreate Ticket · write
Git provider · 1
add_labelsAdd Labels · write
Status · 1
update_statusUpdate Status · write
Related playbooks
Ticket Triage
Classifies new tracker tickets, checks they are actionable, and routes them.
Duplicate Issue Detector
Compares new issues against existing open ones and links likely duplicates.
Stale Issue Reaper
Weekly sweep that classifies quiet issues by reason, nudges them, and flags the oldest for closure.