github-issue-triagelisted

**UTILITY SKILL** — Issue triage (labels + comments), not autofix or PR creation. ## Input - **Automation:** detect JSON in the prompt with issue facts from `detect_issue.sh`. Read `may_edit` from `## Constraints`. - **Interactive:** natural-language Issue URL or number; same label/comment rules. ## Output Specification Session report per [common-output-format.md](references/common-output-format.md). Side effects are GitHub Issue labels and comments via `gh`, not repository file edits. ## Execution Scope ### USE FOR: - Classify Issue type when confident (`bug`, `feature`, `question`, `documentation`) - Drive label FSM (`needs-triage`, `triage:needs-info`, `triage:ready`, `triage:failed`) per [category-fsm.md](references/category-fsm.md) - Post analysis and clarifying questions as Issue comments - On `triage:ready` with human `autofix` label, detect may request dispatch; **Agent must not** HTTP-dispatch or run autofix ### DO NOT USE FOR: - Opening or revising PRs (github-issue-autofix / github-pr-revise) - Firing `repository_dispatch` or starting github-issue-autofix from the Agent (trusted detect hook only) - Mentions / `@` triggers - Applying labels outside `scripts/labels.json` - Relying on AskUserQuestion — questions go to the Issue thread ## Reference Files Guide - [category-fsm.md](references/category-fsm.md) (always read) - [category-prompt-rules.md](references/category-prompt-rules.md) (always read) - [common-checklist.md](references/common-checklist.md) (al