triage

Move GitHub issues through a triage state machine with categorization, reproduction, and agent-ready briefs.

1|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/mst-software-vn/mst-checkscam --skill triage-mst-software-vn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/mst-software-vn/mst-checkscam/tree/main/.claude/skills/triage
Command: npx skills add https://github.com/mst-software-vn/mst-checkscam --skill triage-mst-software-vn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers drown in unlabeled, underspecified issues and lose track of which ones are ready for work. This Skill provides a structured triage workflow that categorizes issues, reproduces bugs, grills reporters for missing detail, and produces durable agent-ready briefs. ## Core Features & Use Cases - State machine triage: Move issues through needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix states with one category label (bug or enhancement). - Agent brief generation: Write durable, behavior-focused specifications with acceptance criteria that stay valid as the codebase changes. - Out-of-scope knowledge base: Record rejected feature requests in .out-of-scope/ files and surface prior rejections when similar issues arrive. - Use Case: A maintainer runs triage on a backlog of 30 issues, reproduces two bugs, requests info on three vague reports, and publishes agent briefs for five well-understood enhancements. ## Quick Start Ask the assistant to show all issues needing attention and triage issue number 42 through to ready-for-agent.

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 and describe what you want in natural language, such as showing issues needing attention or moving a specific issue to a state. The assistant gathers context, recommends a category and state, and applies labels and comments after your confirmation.

What is an agent brief for GitHub issues?▼

An agent brief is a structured comment posted when an issue moves to ready-for-agent. It describes current and desired behavior, key interfaces, testable acceptance criteria, and explicit out-of-scope boundaries so an autonomous agent can implement it without further clarification.

How do I handle rejected feature requests without losing context?▼

Write rejected enhancements to an `.out-of-scope/` directory with one markdown file per concept capturing the decision, reasoning, and prior request links. During future triage, new issues are matched against these files to surface prior rejections instead of re-litigating them.

Can the triage workflow reproduce reported bugs automatically?▼

Yes, for bug reports the workflow attempts reproduction before further questioning by reading the reporter's steps, tracing relevant code, and running tests or commands. A confirmed reproduction strengthens the agent brief, while insufficient detail signals a needs-info state.

What issue states does a triage state machine need?▼

This workflow uses five states: needs-triage for new evaluation, needs-info when waiting on the reporter, ready-for-agent for fully specified work, ready-for-human for judgment-dependent tasks, and wontfix for rejected items. Each issue also carries one category label: bug or enhancement.