What problem does it solve?
Manually triaging GitHub issues is inconsistent, time-consuming, and often loses critical context like prior rejected feature requests or agent handoff specifications, leading to repeated work, misrouted issues, and wasted engineering time for maintainers.
Core Features & Use Cases
- State machine-driven issue routing: Automatically classify issues as bugs or enhancements, then assign canonical state roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) to ensure consistent, predictable workflow progression.
- Durable agent brief generation: Create path-agnostic, behavior-focused specifications for issues ready for AFK agents, avoiding stale file path or line number references that break as the codebase evolves.
- Out-of-scope knowledge base: Track rejected feature requests in a structured directory to preserve institutional reasoning and surface prior rejections when similar new issues are submitted, preventing re-litigation of settled decisions.
- Use Case: Open source maintainers handling high volumes of GitHub issues can use this skill to automate initial classification, ensure consistent routing, and reduce repetitive work on previously rejected feature requests.
Quick Start
Ask the triage skill to list all GitHub issues requiring your attention, sorted by oldest first, with one-line summaries for each.