triage

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

3|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/craft-ts/craft-ts --skill triage-craft-ts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/craft-ts/craft-ts/tree/main/.agents/skills/triage
Command: npx skills add https://github.com/craft-ts/craft-ts --skill triage-craft-ts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers of open-source projects face a constant stream of incoming bug reports and feature requests that need consistent classification, reproduction, and preparation before work can begin. This Skill moves issues through a defined state machine of triage roles so every issue ends up with a clear category, state, and actionable specification. ## Core Features & Use Cases - State machine triage: Moves issues through category roles (bug, enhancement) and state roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) with conflict detection. - Agent brief generation: Produces durable, behavior-focused agent briefs with acceptance criteria so AFK agents can implement issues without re-reading stale context. - Out-of-scope knowledge base: Records rejected feature requests in .out-of-scope/ files and surfaces prior rejections when similar requests reappear. - Use Case: A maintainer runs triage on a backlog of 20 unlabeled issues; the Skill buckets them by attention needed, reproduces reported bugs, grills reporters for missing detail, and posts ready-to-implement briefs on approved issues. ## Quick Start Ask the assistant to show all issues that need triage attention and then triage a specific issue number 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 in natural language, such as asking to see issues needing attention or to triage a specific issue number. The assistant reads the full issue, recommends a category and state, reproduces bugs, and applies labels with explanatory comments.

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.

How do I track rejected feature requests in a repository?▼

Rejected enhancements are recorded as Markdown files in a .out-of-scope/ directory, one file per concept, capturing the decision, reasoning, and links to prior requests. During triage, new issues are matched against these files to surface previous rejections.

Can I override the triage state of an issue directly?▼

Yes, maintainers can issue direct commands like moving an issue to ready-for-agent, and the assistant applies the role after confirming the changes. Grilling sessions are skipped, though it asks whether an agent brief should be 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, it posts structured triage notes listing what is established and specific actionable questions, then labels the issue needs-info until the reporter replies.