issue-triage

# Issue Triage Triage GitHub issues rigorously and without overwhelming the user: first narrow down WHICH issues to look at, then deep-triage each selected issue in parallel, then recommend concrete actions (close / fix / keep / needs-info) for the owner to approve. This is the issue-side companion to `pr-vetting`. It reuses the same orchestration scaffold (main agent orchestrates, one subagent per item, gitignored work dir, merged summary) but drops everything that only makes sense for incoming code (deep security audit, contributor reputation, merge-policy stances, mass-PR detection). ## When to use - The user asks to triage / review / clean up issues, or asks "which issues are still open / can be closed / are worth doing". - After a milestone, to sweep stale issues. ## Core principles - **Never dump all issues at once (selection first).** The point is to help the user decide, not to bury them. Always run the selection stage (Step 1) before any deep triage. - **Orchestrate.** One subagent per selected issue writes an independent file; the main agent merges a short summary. Keeps context lean and each triage focused. - **Recommend, do not act.** The skill proposes close/fix/keep/needs-info and provides ready-to-use comment text, but the owner decides. The main agent only closes / comments / pushes after explicit approval. - **Careful public wording.** Any text that will be posted publicly (close comments, replies) must be phrased carefully and must NOT box ...