triage

Automate GitHub issue classification and state management with role-based workflows.

1|Updated Aug 1, 2020
One-click install
npx skills add https://github.com/JohannesKonings/JohannesKonings.github.io --skill triage-johanneskonings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/JohannesKonings/JohannesKonings.github.io/tree/main/.agents/skills/triage
Command: npx skills add https://github.com/JohannesKonings/JohannesKonings.github.io --skill triage-johanneskonings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing GitHub issue backlogs manually is time-consuming and error-prone, with issues often left unlabeled, misclassified, or stuck in limbo without clear ownership or next steps. This Skill automates the entire triage workflow to ensure issues are consistently classified, prioritized, and routed to the right team or AI agent.

Core Features & Use Cases

  • Role-based state machine: Automatically classifies issues as bugs or enhancements and assigns canonical state roles (needs-triage, ready-for-agent, wontfix, etc.) to standardize workflow.
  • Durable agent brief generation: Creates structured, future-proof specifications for AFK agents that avoid referencing stale file paths or line numbers.
  • Out-of-scope knowledge base: Tracks rejected feature requests to prevent re-litigating old decisions and deduplicate similar incoming issues.
  • Use Case: For an open source project receiving 50+ new GitHub issues a week, use this Skill to quickly sort incoming reports, identify which are ready for AI implementation, and document rejected features to reduce repetitive feedback.

Quick Start

Use the triage skill to show me all GitHub issues that need my attention right now.

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 for a high-volume open source backlog?

Automating GitHub issue triage uses a role-based state machine to classify incoming bug reports and feature requests, assigning canonical states like needs-triage or ready-for-agent to eliminate manual sorting overhead. It ensures consistent routing for high-volume repositories.

What is the best way to generate agent briefs for AI coding tasks from GitHub issues?

Generating durable agent briefs for AI coding tasks creates structured, future-proof specifications from GitHub issues that avoid referencing stale file paths or line numbers, ensuring AFK agents receive stable implementation instructions without manual context assembly.

How do I prevent duplicate feature requests in my GitHub issue tracker?

Preventing duplicate feature requests involves maintaining an out-of-scope knowledge base that tracks rejected features, stopping users from re-litigating old decisions and deduplicating similar incoming issues to keep the tracker focused on active work.

Does this automated issue classification work for both bug reports and feature requests?

Automated issue classification works for both bug reports and feature requests by applying a role-based state machine that categorizes issues into canonical state roles like needs-triage, ready-for-agent, or wontfix, standardizing the handling workflow for both types.

Can I use this workflow automation to route issues directly to AFK AI agents?

You can use this workflow automation to route issues directly to AFK AI agents by setting issue states to ready-for-agent and generating durable agent briefs, providing structured specifications that autonomous coding agents need to begin implementation immediately.