One-click install
npx skills add https://github.com/Herxinsasa/Skills-Collector --skill triage-herxinsasa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/Herxinsasa/Skills-Collector/tree/main/mattpocock-skills/skills/engineering/triage
Command: npx skills add https://github.com/Herxinsasa/Skills-Collector --skill triage-herxinsasa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of disorganized GitHub issue tracking, where unlabeled, misclassified, or under-specified issues slow down development teams and make it difficult to assign work to human developers or autonomous agents efficiently.

Core Features & Use Cases

  • Standardized Issue Classification: Uses a state machine with defined category (bug/enhancement) and state roles (needs-triage, ready-for-agent, wontfix, etc.) to consistently label and route issues.
  • Durable Agent Brief Generation: Creates structured, future-proof agent briefs for issues ready for autonomous agents, avoiding stale references to file paths or line numbers.
  • Out-of-Scope Knowledge Base: Tracks rejected feature requests in a dedicated directory to preserve institutional memory and prevent redundant re-litigation of prior decisions.
  • Use Case: For an open source development team, use this Skill to quickly sort incoming bug reports and feature requests, assign them to the right team members or AI agents, and avoid re-discussing previously rejected feature ideas.

Quick Start

Use the triage skill to review all unlabeled issues in your GitHub repository and recommend which ones should be moved to ready-for-agent status for autonomous processing.

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

Automate GitHub issue triage by applying a standardized state machine that classifies bug reports and feature requests into defined category and state roles, routing them to human developers or autonomous agents. This consistently labels incoming issues and preserves institutional memory of prior decisions.

How do I generate durable agent briefs for autonomous GitHub issue processing?

Generate durable agent briefs by creating structured, future-proof issue summaries that avoid stale references to file paths or line numbers. This prepares issues marked ready-for-agent for autonomous processing without breaking when code changes.

What is the best way to track rejected feature requests in GitHub repositories?

Track rejected feature requests by maintaining a dedicated out-of-scope knowledge base directory. This preserves institutional memory, prevents redundant re-litigation of prior decisions, and stops teams from repeatedly discussing previously rejected ideas.

Can I use a state machine to classify and route unlabeled GitHub issues?

Yes, use a state machine with defined category and state roles like needs-triage, ready-for-agent, and wontfix to consistently label and route unlabeled GitHub issues. This solves disorganized tracking by standardizing assignment to developers or autonomous agents.

How do I prevent redundant discussions about previously rejected GitHub features?

Prevent redundant discussions by tracking rejected feature requests in a dedicated out-of-scope knowledge base directory. This maintains institutional memory of prior triage decisions and reduces repetitive re-litigation across the development team.