triage-issues

Automate triage and labeling of open GitHub issues by analyzing content.

1|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/dyoshikawa/webseek --skill triage-issues-dyoshikawa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-issues
Source: https://github.com/dyoshikawa/webseek/tree/main/.rulesync/skills/triage-issues
Command: npx skills add https://github.com/dyoshikawa/webseek --skill triage-issues-dyoshikawa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual overhead of managing incoming GitHub issues by automatically identifying unlabeled items and applying appropriate categorization based on their content.

Core Features & Use Cases

  • Automated Triage: Scans for unlabeled open issues to ensure no community feedback or bug report is overlooked.
  • Context-Aware Labeling: Analyzes issue descriptions and comments to apply precise labels like bug, enhancement, or documentation.
  • Use Case: Maintainers can run this skill to quickly organize a backlog of new issues, ensuring that contributors can easily find tasks labeled as good first issue or help wanted.

Quick Start

Run the triage-issues skill to scan the repository for unlabeled issues and apply the correct labels based on their content.

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 unlabeled open issues?

Automate GitHub issue triage by scanning open unlabeled issues and applying labels like bug or enhancement based on analyzed content and metadata. This ensures no community feedback is overlooked during repository maintenance.

Do I need the GitHub CLI installed to label issues automatically?

Yes, you need the GitHub CLI (gh) installed and authenticated to label issues automatically. The CLI handles the repository API interactions required to scan issues and apply categorization tags.

What's the best way to automatically categorize a backlog of new GitHub issues?

The best way to categorize a backlog of new GitHub issues is to run an automated triage skill that analyzes descriptions and comments to apply precise labels. This helps contributors find tasks marked as good first issue or help wanted.

Can I automatically identify and label bug reports versus enhancements in GitHub?

Yes, you can automatically identify and label bug reports versus enhancements in GitHub. The triage mechanism analyzes issue content and metadata to distinguish between bugs, enhancements, and documentation needs before applying the correct tags.

How does context-aware issue labeling work for repository maintenance?

Context-aware issue labeling works by analyzing the text of issue descriptions and comments to determine the appropriate category. It then applies precise labels automatically, ensuring consistent backlog management across the repository.

When should I not use automated issue triage for my repository?

You should not use automated issue triage when your repository lacks a clear labeling taxonomy or when issues require complex human judgment that content analysis cannot provide. It is designed for consistent categorization of standard backlog items.