triage

Automate issue triage and generate structured agent briefs.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/Lev-it/lev-skills --skill triage-lev-it
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/Lev-it/lev-skills/tree/main/.claude/skills/triage
Command: npx skills add https://github.com/Lev-it/lev-skills --skill triage-lev-it

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The triage Skill streamlines the process of categorizing and moving issues through a triage workflow in project issue trackers, enhancing efficiency and clarity in issue management.

Core Features & Use Cases

  • Structured Agent Briefs: Generates clear, durable agent briefs for GitHub issues, detailing desired behaviors and acceptance criteria.
  • State Machine Management: Facilitates state transitions for issues like moving from 'needs-triage' to 'ready-for-agent'.
  • Contextual Issue Analysis: Provides context for issue triage by referencing codebase, design documents, and historical out-of-scope records.

Quick Start

To begin triage, run the '/triage' command with the issue identifier.

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 with structured agent briefs?

Automating GitHub issue triage involves categorizing issues into bugs or enhancements and generating structured agent briefs that detail desired behaviors and acceptance criteria. This Skill manages state transitions to move issues from 'needs-triage' to 'ready-for-agent'.

What is the issue triage state machine and how does it work?

An issue triage state machine manages transitions between predefined states such as 'needs-triage', 'needs-info', 'ready-for-agent', 'ready-for-human', and 'wontfix'. It streamlines workflows by enforcing structured status changes based on issue categorization and contextual analysis.

How do I categorize GitHub issues as bugs or enhancements during triage?

Categorizing GitHub issues as bugs or enhancements during triage requires referencing the codebase, design documents, and historical out-of-scope records. This contextual analysis ensures accurate classification before generating a structured agent brief for the issue.

Do I need to understand my project's issue tracker labeling system to use automated triage?

Yes, understanding your project's issue tracker labeling system is required for automated triage. Accurate issue categorization and state transitions depend on mapping existing labels to defined states like 'needs-info' or 'ready-for-human' for proper workflow management.

When should I move a triaged issue to 'needs-info' instead of 'ready-for-agent'?

Move a triaged issue to 'needs-info' when contextual analysis indicates missing details from the codebase or design documents. If the issue has sufficient context and clear acceptance criteria, it transitions to 'ready-for-agent' for automated brief generation.

Can I use issue triage state transitions for issues that are out of scope?

Yes, issue triage state transitions handle out-of-scope items by referencing historical out-of-scope records during contextual analysis. When an issue is confirmed out of scope, the state machine transitions it directly to the 'wontfix' state.