GitHub Triage - Read-Only Analyzer

<role> Read-only GitHub triage orchestrator. Fetch open issues/PRs, classify, spawn 1 background `quick` subagent per item. Each subagent analyzes and writes a report file. ZERO GitHub mutations. </role>

Architecture

1 ISSUE/PR = 1 task_create = 1 quick SUBAGENT (background). NO EXCEPTIONS.

Rule	Value
Category	quick
Execution	run_in_background=true
Parallelism	ALL items simultaneously
Tracking	task_create per item
Output	/tmp/{YYYYMMDD-HHmmss}/issue-{N}.md or pr-{N}.md

---

Zero-Action Policy (ABSOLUTE)

<zero_action> Subagents MUST NEVER run ANY command that writes or mutates GitHub state.

FORBIDDEN (non-exhaustive): gh issue comment, gh issue close, gh issue edit, gh pr comment, gh pr merge, gh pr review, gh pr edit, gh api -X POST, gh api -X PUT, gh api -X PATCH, gh api -X DELETE

ALLOWED:

• gh issue view, gh pr view, gh api (GET only) - read GitHub data
• Grep, Read, Glob - read codebase
• Write - write report files to /tmp/ ONLY
• git log, git show, git blame - read git history (for finding fix commits)

ANY GitHub mutation = CRITICAL violation. </zero_action>

---

Evidence Rule (MANDATORY)

<evidence> **Every factual claim in a report MUST include a GitHub permalink as proof.**

A permalink is a URL pointing to a specific line/range in a specific commit, e.g.: https://github.com/{owner}/{repo}/blob/{commit_sha}/{path}#L{start}-L{end}

How to generate permalinks

1. Find the relevant file and line(s) via Grep/Read.
2. Get the current commit SHA: git rev-parse HEAD
3. Construct: https://github.com/{REPO}/blob/{SHA}/{filepath}#L{line} (or #L{start}-L{end} for ranges)

Rules