triage

Classify and prioritize GitHub issues through a structured state machine.

Updated May 9, 2026
One-click install
npx skills add https://github.com/kk20300113-png/my-claude-skills --skill triage-kk20300113-png
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/kk20300113-png/my-claude-skills/tree/main/triage
Command: npx skills add https://github.com/kk20300113-png/my-claude-skills --skill triage-kk20300113-png

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub issue trackers often become disorganized with unlabeled issues, lack of context for implementers, and repeated discussions of previously rejected feature requests. This Skill eliminates that friction by providing a structured, consistent workflow for issue classification, prioritization, and handoff to human or AI implementers.

Core Features & Use Cases

  • Structured Issue Classification: Categorize issues as bugs or enhancements, and assign canonical state roles (needs-triage, ready-for-agent, wontfix etc.) to track progress through the workflow.
  • Durable Agent Brief Generation: Create implementation-ready specifications for AFK agents that avoid stale file path and line number references, staying useful even as the codebase evolves.
  • Out-of-Scope Knowledge Base: Document rejected feature requests with reasoning to prevent duplicate discussions and preserve institutional memory for future triage decisions.
  • Use Case: For a team with 200+ open GitHub issues, use this Skill to quickly identify which issues need maintainer attention, prepare detailed specs for agent implementation, and avoid re-litigating previously rejected feature requests.

Quick Start

Invoke the triage skill to review your GitHub issue queue, classify pending issues by type and priority, and generate agent-ready briefs for implementation tasks.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I organize and prioritize unlabeled GitHub issues for bug tracking?

GitHub issue triage is managed through a structured state machine that classifies and prioritizes issues by type, assigning canonical state roles like needs-triage or ready-for-agent to track workflow progress.

What is the best way to generate implementation-ready agent briefs for software maintenance?

Implementation-ready agent briefs are generated as durable specifications that avoid stale file path and line number references, ensuring the implementation context remains useful even as the codebase evolves.

How do I stop repeated discussions of previously rejected feature requests on GitHub?

Rejected feature requests are documented in an out-of-scope knowledge base with reasoning, preserving institutional memory to prevent duplicate discussions and inform future triage decisions.

Can I use this workflow automation to handle a queue of 200+ open GitHub issues?

This workflow automation handles large queues of 200+ open GitHub issues by quickly identifying which need maintainer attention, preparing detailed specs, and filtering out previously rejected requests.

Does this issue triage process work for both bug tracking and feature request evaluation?

Issue triage supports both bug tracking and feature request evaluation by categorizing incoming issues as bugs or enhancements and routing them through a consistent classification and handoff workflow.