skills.rest
borgbase
borgbaseOFFICIAL
Explore all skills by this author →
Website𝕏@borg_baseGitHub

issue-triage

Classify and label GitHub issues for the Vorta project according to triage policy.

2.5k|227|Updated Oct 27, 2018
Search Tags:#workflow#github#issues#triage#decision-making#labels#project-management
One-click install
npx skills add https://github.com/borgbase/vorta --skill issue-triage-borgbase
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-triage
Source: https://github.com/borgbase/vorta/tree/main/.claude/skills/issue-triage
Command: npx skills add https://github.com/borgbase/vorta --skill issue-triage-borgbase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triaging GitHub issues is essential to maintain project momentum, ensuring issues are correctly categorized, prioritized, and routed for action, so the team can respond quickly and consistently.

Core Features & Use Cases

  • Automated classification of incoming issues by type, priority, and suggested actions.
  • Label management that applies and updates labels (type, priority, status, platform) to reflect current state.
  • Issue routing and closure guidance to decide whether to close, escalate, or assign to contributors based on policy and scope.

Quick Start

Review the first new issue and apply initial labels following the triage policy described in this skill.

Frequently Asked Questions about issue-triage

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

FAQPage Schema
How do I triage GitHub issues for a software project?▼

Automated GitHub issue triage applies predefined labels for type, priority, status, and platform to classify tickets and suggest actions. It enforces a consistent taxonomy to help maintainers decide whether to close, escalate, or assign issues.

What is the best way to manage labels on GitHub feature requests and bugs?▼

Managing GitHub issue labels involves applying a defined taxonomy across type, priority, status, and platform categories. Consistent label application categorizes bugs and feature requests accurately, enabling maintainers to track issue states and route tickets effectively.

How do I decide whether to close, escalate, or reassign GitHub issues?▼

Deciding to close, escalate, or reassign GitHub issues depends on evaluating the ticket against a triage policy. Apply scope and priority criteria to the classified issue to determine the correct resolution path and guide contributor assignments.

Can I use automated issue classification for support tickets and questions?▼

Yes, automated issue classification can process support tickets and questions alongside bugs and feature requests. It applies consistent labels based on a defined taxonomy to ensure every incoming issue is categorized and routed correctly.

What are the limitations of automated GitHub issue triage?▼

Automated GitHub issue triage is limited by its adherence to a predefined taxonomy and specific triage policy. It cannot process issues accurately without established labeling rules and requires manual review for edge cases outside the defined scope.

Related Skills

Explore More Product & Management Skills→
Atypical-ConsultingAtypical-Consulting
2

ghs-issue-triage

Classify and label GitHub issues by type, priority, and status.

Official
Advanced
a2musa2mus

speckit-taskstoissues

Convert tasks.md entries into GitHub issues with labels, assignees, and milestones.

Community
Intermediate
rito528rito528
1

issue-triage

Parse GitHub issue content and apply status labels via the GitHub API.

Community
Intermediate
zerAdazerAda

gsd-execution

Automate the GSD methodology workflow from triage through closure.

Community
Intermediate