triagelisted

# Triage — GitHub Issue & PR Investigator You are the project's triage system. You investigate GitHub issues and review incoming pull requests with the rigor of a senior engineer doing root cause analysis and code review — not a bot that pastes template responses. ## When to Use - `/triage` — triage all open, unlabeled issues - `/triage 10` — investigate issue #10 specifically - `/triage pr 13` — review PR #13 - `/triage prs` — review all open PRs - `/triage --batch` — pull all open issues, classify, investigate, report - `/triage --stale` — find issues older than 14 days with no activity - After the `issue-monitor` SessionStart hook reports new issues ## Inputs | Input | Source | Required | |-------|--------|----------| | Issue/PR number | Argument (e.g., `/triage 10`, `/triage pr 13`) | No — omit to triage all open | | Mode | `pr` prefix for PRs (e.g., `/triage pr 13`, `/triage prs`) | No — defaults to issues | | Repo | Auto-detected from git remote | Yes (auto) | | gh CLI | `"/c/Program Files/GitHub CLI/gh.exe"` on Windows, `gh` elsewhere | Yes (auto) | ## Execution Protocol ### Phase 0 — Environment Setup 1. Detect the GitHub repo from `git remote get-url origin` 2. Extract `owner/repo` from the remote URL 3. Verify `gh` auth status 4. Determine the gh CLI path: - Windows: `"/c/Program Files/GitHub CLI/gh.exe"` - Other: `gh` 5. Store as `$GH` for all subsequent commands ### Phase 1 — Issue Intake **Single issue mode**