triage-issues

Automate GitHub issue triage into bugs and features with severity scoring.

Updated May 7, 2026
One-click install
npx skills add https://github.com/chtugha/brassclaw --skill triage-issues-chtugha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-issues
Source: https://github.com/chtugha/brassclaw/tree/main/.bob/skills/triage-issues
Command: npx skills add https://github.com/chtugha/brassclaw --skill triage-issues-chtugha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github-api, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of triaging open GitHub issues, classifying them into bugs and features, ranking their severity and opportunity, and flagging under-specified issues.

Core Features & Use Cases

  • Automated Issue Triage: Automatically classifies issues into bugs, features, or ambiguous categories based on title, body, and labels.
  • Severity and Opportunity Scoring: Assigns a severity and opportunity score to bugs and features for prioritization.
  • Duplicate Detection: Identifies duplicate and related issues for efficient tracking.
  • Report Generation: Outputs a comprehensive triage report with detailed statistics and recommendations.

Quick Start

Triage open GitHub issues using the 'triage-issues' skill.

Frequently Asked Questions about triage-issues

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

FAQPage Schema
How do I automate GitHub issue triage for bugs and feature requests?

You can automate GitHub issue triage by using a skill that fetches issues via the GitHub API and classifies them into bugs and features. It applies predefined rules to score severity and opportunity, flagging under-specified issues and outputting a structured triage report.

How does automated issue classification rank severity and opportunity?

Automated issue classification ranks severity and opportunity by applying predefined scoring rules to the fetched GitHub issues. It analyzes the text in issue titles and bodies to evaluate priority, ultimately generating a comprehensive triage report with detailed statistics and recommendations.

Do I need the GitHub API to classify and prioritize open issues?

Yes, the GitHub API is required to fetch and analyze open issues for automated triage. The skill depends on the github-api to retrieve issue data, which is then processed to classify bugs and features and flag under-specified issues.

Can automated issue triage detect duplicate GitHub issues?

Yes, automated issue triage can identify duplicate and related GitHub issues for efficient tracking. Alongside classifying issues into bugs and features and scoring severity, it processes issue content to detect duplicates and outputs these findings in a comprehensive report.

What is the best way to flag under-specified GitHub issues automatically?

The best way to flag under-specified GitHub issues is through automated triage that analyzes issue titles and bodies via the GitHub API. By evaluating content against predefined rules, it identifies ambiguous issues lacking sufficient detail and highlights them in a structured report.