triage

Automate GitHub issue triage with role-based state transitions and bug/enhancement categorization.

1|Updated May 22, 2026
One-click install
npx skills add https://github.com/spontus-reach/spontus --skill triage-spontus-reach
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/spontus-reach/spontus/tree/main/.agents/skills/triage
Command: npx skills add https://github.com/spontus-reach/spontus --skill triage-spontus-reach

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams quickly classify and route GitHub issues by ensuring every issue moves through the right triage states with clear, durable instructions.

Core Features & Use Cases

  • Triage state machine: Moves issues between canonical roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) with category correctness (bug vs enhancement).
  • Agent brief generation: Produces durable AFK agent briefs that specify contracts, interfaces, and acceptance criteria.
  • Out-of-scope knowledge capture: Writes and surfaces prior enhancement rejections via the .out-of-scope knowledge base to reduce repeated debates.
  • Reporter clarification: Uses a structured needs-info template to request specific missing details before proceeding.

Quick Start

Use the triage skill to route an issue you selected, for example: "Move issue #42 to ready-for-agent after summarizing context and confirming the best category and state."

Frequently Asked Questions about triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub issue triage to classify bugs and feature requests?

Automating GitHub issue triage moves issues through a role-based state machine, categorizing them as bugs or enhancements while applying canonical labels like needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix.

How do I generate durable agent briefs for GitHub issues ready for delivery?

Generating durable agent briefs for GitHub issues involves creating AFK agent instructions that specify contracts, interfaces, and acceptance criteria, moving items from needs-triage to ready-for-agent states.

What is the best way to handle out-of-scope enhancement requests and prevent duplicate debates?

Handling out-of-scope enhancement requests involves documenting wontfix decisions in the .out-of-scope knowledge base, reducing repeated debates by surfacing prior rejections when similar new feature requests are triaged.

How do I request missing information from reporters during GitHub bug triage?

Requesting missing information during GitHub bug triage uses a structured needs-info template to prompt reporters for specific missing details before proceeding to ready-for-human or ready-for-agent states.

Does the triage workflow support moving issues directly to wontfix for enhancement requests?

Moving issues directly to wontfix for enhancement requests is supported by the triage state machine, which enforces category correctness and documents the rejection rationale within the out-of-scope knowledge base.

Can I enforce canonical category and state label consistency across GitHub issue workflows?

Enforcing canonical category and state label consistency is achieved by the triage state machine, ensuring every GitHub issue maintains strict bug or enhancement categorization alongside valid triage state labels.