triage

Classify GitHub issues as bugs or enhancements and manage state transitions.

Updated May 15, 2026
One-click install
npx skills add https://github.com/ruskibeats/t1d --skill triage-ruskibeats
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/ruskibeats/t1d/tree/main/.agents/skills-archive/engineering/triage
Command: npx skills add https://github.com/ruskibeats/t1d --skill triage-ruskibeats

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Manages issue triage on GitHub repositories by categorizing and prioritizing issues using AI-driven insights.

Core Features & Use Cases

  • Automated Triage: Classifies issues as 'bug' or 'enhancement' based on content.
  • State Machine: Manages issue state transitions (e.g., from 'needs-triage' to 'ready-for-agent').
  • Out-of-Scope Documentation: Tracks and surfaces previously rejected features to prevent duplicates.
  • Use Case: Simplify the issue management process by automating the initial stages of triage, allowing maintainers to focus on critical tasks.

Quick Start

/triage #42

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 to classify bugs and enhancements?

Automated issue triage uses AI to classify GitHub issues as 'bug' or 'enhancement' based on content, streamlining issue management by reducing manual categorization effort for maintainers.

What is the best way to prevent duplicate feature requests in GitHub repositories?

To prevent duplicate feature requests, issue management tools link new proposals to previously rejected features, maintaining out-of-scope documentation that surfaces prior decisions and avoids redundant submissions.

How do I manage GitHub issue state transitions from needs-triage to ready-for-agent?

Managing issue state transitions involves a state machine that moves GitHub issues from 'needs-triage' to 'ready-for-agent', ensuring structured progression through the triage workflow.

Can AI-driven triage handle large GitHub repositories with many open issues?

AI-driven triage scales issue management for GitHub repositories by automating the initial categorization and prioritization stages, allowing maintainers to focus on critical tasks regardless of volume.

What are the limitations of using AI for bug tracking and issue classification?

AI-driven bug tracking classifies issues based on content, but limitations include potential misclassification of ambiguous reports and the need for human oversight when managing complex state transitions.