# triage

This subagent reviews GitHub issues with github-triage, applies labels, and routes issues to people under explicit assignment rules.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 7523 repo stars
- Author: Devin-AXIS
- License: LicenseRef-Proprietary · policy=link-only · description only; the file stays with the author
- Source: https://github.com/Devin-AXIS/iPolloWork/tree/HEAD/.opencode/agents/triage.md
- Updated: 2026-10-29
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/triage

## What it does

\`triage` uses `github-triage` to inspect GitHub issues and classify them. Its rules cover Windows mentions, RAM or CPU problems, the desktop app and `opencode web`, nix, zen, documentation requests, and selected OpenTUI symptoms. LLM response time does not qualify for the performance label.

It also decides who should receive an issue. `adamdotdev` is reserved for desktop cases, `fwang` for zen cases, and `jayair` for documentation work. Other issues follow the remaining assignment guidance. Without the `github-triage` tool, the subagent cannot perform issue triage.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/agents/triage.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/triage.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/triage.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/Devin-AXIS/iPolloWork/tree/HEAD/.opencode/agents/triage.md

## When to use it
- label GitHub issues by symptom
- separate desktop reports from terminal and TUI problems
- spot issues involving high RAM or CPU use
- route labelled issues to the right contributor
- identify requests for documentation changes

## Example prompts
- Review the new GitHub issues and apply the triage labels.
- Classify this Windows issue and assign it according to the triage rules.
- Check whether this `opencode web` report is a desktop issue or a general TUI problem.

## Similar
- [oss-issue-triage](https://affpapa.org/en/nevibecode/skills/oss-issue-triage.md) — skill · 13400 installs
- [issue-triage](https://affpapa.org/en/nevibecode/skills/decebals-issue-triage.md) — skill · 254 installs
- [github-project-triage](https://affpapa.org/en/nevibecode/skills/github-project-triage.md) — skill · 105 installs
- [backlog-swipe-triage](https://affpapa.org/en/nevibecode/plugins/backlog-swipe-triage.md) — plugin · ★ 41430 repo stars
- [loop-triage](https://affpapa.org/en/nevibecode/skills/loop-triage.md) — skill · ★ 11819 repo stars
- [triage-issues](https://affpapa.org/en/nevibecode/skills/triage-issues.md) — skill · ★ 1636 repo stars

From the same set: [devin-axis/ipollowork](https://affpapa.org/en/nevibecode/by/devin-axis/ipollowork.md) — 42 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
