Issue Triage

This handles the tedious work of categorizing GitHub issues into bugs, feature requests, questions, or duplicates, then assigns priority labels from critical to low based on impact. You'd run it when someone says "triage issues" or during weekly maintenance to clear backlogs. The workflow is solid: it walks through fetching issues via GitHub MCP or gh CLI, provides clear criteria for each category (stack traces mean bug, "how do I" means question), and includes response templates for common scenarios. The token optimization advice is actually useful, like batching 10 issues in one prompt instead of processing them individually, which cuts token usage by around 60%. Works best if you've got the GitHub MCP server configured, though it'll fall back to CLI commands if needed.