github-triagelisted

# GitHub Triage — Unified Issue & PR Processor ## Tool Restrictions Read-only GitHub and repository analysis. Do not modify repo files or GitHub state. Local report writes are allowed only under `/tmp/opencode/github-triage-{datetime}/`. MCP tools: `notepad_write`, `evidence_log`, `ast_search`. Fetch open issue/PR metadata, classify each, spawn 1 background executor per item. Each subagent fetches full details for its item and writes a report under `/tmp/opencode/github-triage-{datetime}/`. Never take destructive action. ## Zero-Action Policy (NON-NEGOTIABLE) **NEVER run any GitHub mutation command.** This skill is read-and-report ONLY. Forbidden commands (automatic failure if used): - `gh pr merge` — NEVER - `gh pr close` — NEVER - `gh issue close` — NEVER - `gh issue edit` — NEVER - `gh pr edit` — NEVER - `gh pr review --approve` — NEVER - `gh api` with non-GET methods — NEVER (`POST`, `PUT`, `PATCH`, `DELETE` are forbidden) - Any `gh` command that writes, modifies, or deletes Allowed read-only commands: - `gh issue list`, `gh issue view` - `gh pr list`, `gh pr view` - `gh api --method GET repos/{REPO}/pulls/{number}/files` - `gh repo view` Violation = CRITICAL FAILURE. Report only; humans decide. ## Evidence Rule (MANDATORY) Every factual claim MUST cite a GitHub permalink containing a commit SHA. Branch permalinks (`blob/main`, `blob/master`, branch names) are forbidden. Format: ``` CLAIM: "The handler for X is in Y" EVIDENCE: https://github.com/{REPO}/blob/{CO