triage

Classify and route GitHub issues through a state machine workflow.

25|5|Updated Apr 22, 2017
One-click install
npx skills add https://github.com/assofohdz/subspace-infinity --skill triage-assofohdz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/assofohdz/subspace-infinity/tree/main/.agents/skills/triage
Command: npx skills add https://github.com/assofohdz/subspace-infinity --skill triage-assofohdz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the chaos of unorganized GitHub issue tracking, where unlabeled issues, unclear task ownership, and repeated discussions of rejected features waste maintainer time and delay project progress.

Core Features & Use Cases

  • State Machine Workflow: Automatically routes issues through defined triage states (needs-triage, ready-for-agent, wontfix etc.) with clear category assignment for bugs and enhancements.
  • Durable Agent Briefs: Generates context-rich, stale-resistant briefs for AFK agents to implement issues without relying on fragile file paths or line numbers.
  • Out-of-Scope Knowledge Base: Tracks rejected feature requests with reasoning to avoid re-litigating past decisions and deduplicate similar incoming issues.
  • Use Case: For a solo maintainer of an open-source Java game engine receiving 10+ weekly issues, use this skill to quickly sort new bug reports, prepare actionable tasks for contributors, and automatically reference past rejections of duplicate feature requests.

Quick Start

Use the triage skill to review all unlabeled issues in the repository and provide a prioritized summary of which need immediate maintainer attention.

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 bug tracking and feature requests?

Automating GitHub issue triage involves using a state machine workflow to classify bugs and route feature requests, reducing maintainer overhead. This ensures clear category assignment and tracks rejected features to deduplicate similar incoming issues efficiently.

What is the best way to prepare actionable agent briefs for GitHub project maintenance?

The best way to prepare actionable agent briefs is to generate durable, context-rich summaries for AFK agents. This allows them to implement issues without relying on fragile file paths or line numbers, ensuring task execution remains stable over time.

How does a state machine workflow help with issue classification in software projects?

A state machine workflow helps with issue classification by automatically routing GitHub issues through defined triage states like needs-triage, ready-for-agent, and wontfix. This enforces clear workflow state transitions and assigns distinct categories for bugs and enhancements.

Can I track rejected feature requests to avoid re-litigating past decisions on GitHub?

Yes, you can track rejected feature requests by maintaining an out-of-scope knowledge base. This records past rejections with reasoning to avoid re-litigating decisions and automatically deduplicates similar incoming issues for project maintenance teams.

Does this issue triage approach work for solo maintainers handling high issue volumes?

Yes, this issue triage approach works for solo maintainers handling high issue volumes by quickly sorting new bug reports and preparing actionable tasks. It efficiently manages weekly influxes of issues by providing a prioritized summary for immediate attention.