triage

Triage GitHub issues through a label-driven state machine with agent briefs.

Updated May 7, 2026
One-click install
npx skills add https://github.com/Pieter-1337/Euricom-tsz --skill triage-pieter-1337
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/Pieter-1337/Euricom-tsz/tree/main/.claude/skills/matt-triage
Command: npx skills add https://github.com/Pieter-1337/Euricom-tsz --skill triage-pieter-1337

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers drown in untriaged issues: bugs without reproductions, feature requests without specs, and no durable record of why features were rejected. This Skill moves issues through a structured state machine so every issue ends up classified, specified, and routed to the right owner. ## Core Features & Use Cases - State machine triage: Classify issues with category roles (bug, enhancement) and state roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix), with conflict detection and maintainer overrides. - Agent brief generation: Produce durable, behavior-focused agent briefs with acceptance criteria so AFK agents can implement issues without re-reading stale file paths. - Out-of-scope knowledge base: Record rejected feature requests in .out-of-scope/ files and surface prior rejections when similar requests reappear. - Use Case: A maintainer runs triage on Monday morning, sees three buckets of issues needing attention, reproduces a reported bug, grills the reporter on a vague feature request, and moves two issues to ready-for-agent with complete briefs. ## Quick Start Ask the assistant to show you everything on the issue tracker that needs triage attention, or tell it to triage a specific issue number.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I triage GitHub issues with an AI assistant?

Invoke the triage workflow in natural language, such as asking what needs attention or naming a specific issue number. The assistant reads the full issue, recommends a category and state, and applies labels, comments, or closures after your confirmation.

What is an agent brief for GitHub issues?

An agent brief is a structured issue comment that serves as the authoritative spec for an autonomous coding agent. It describes current and desired behavior, key interfaces, testable acceptance criteria, and explicit out-of-scope boundaries, avoiding file paths and line numbers that go stale.

How does the out-of-scope knowledge base prevent duplicate feature requests?

Rejected enhancements are recorded as concept files in an .out-of-scope/ directory with the decision, reasoning, and links to prior requests. During triage, new issues are matched against these files by concept similarity so prior rejections can be surfaced instead of re-litigated.

Can I move an issue directly to ready-for-agent without a full triage session?

Yes, a quick state override lets you command a direct transition such as moving an issue to ready-for-agent. The assistant confirms the role changes, comments, and closures before acting, and asks whether you want an agent brief written.

What happens when a bug report lacks enough detail to reproduce?

The assistant attempts reproduction from the reporter's steps first. If detail is insufficient, the issue moves to needs-info with triage notes listing what was established and specific actionable questions for the reporter, so prior progress is never lost.