issue-triage

Assign structured labels and priorities to GitHub issues via the GitHub API.

8|2|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/SebastienDegodez/skraft-plugin --skill issue-triage-sebastiendegodez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-triage
Source: https://github.com/SebastienDegodez/skraft-plugin/tree/main/plugins/skills/issue-triage
Command: npx skills add https://github.com/SebastienDegodez/skraft-plugin --skill issue-triage-sebastiendegodez

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Manages the classification and prioritization of GitHub issues, streamlining the triage process and ensuring issues are appropriately labeled and prioritized for further discussion and development.

Core Features & Use Cases

  • Structured Label Taxonomy: Assigns predefined labels for type, priority, effort, and status.
  • Priority Framework: Determines issue importance based on urgency and business impact.
  • Effort Estimation: Categorizes issues into effort levels (XS, S, M, L, XL) for sprint planning.
  • Duplicate Detection: Identifies and links duplicate issues to avoid redundant work.
  • Triage Report: Generates a comprehensive report for sprint planning.

Quick Start

Apply the issue-triage skill to a new GitHub issue to automatically assign appropriate labels and priority.

Frequently Asked Questions about issue-triage

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

FAQPage Schema
How do I automatically classify and prioritize GitHub issues for sprint planning?

Automatically classifying and prioritizing GitHub issues involves assigning structured labels for type, priority, effort, and status. This process streamlines issue triage and generates a comprehensive report to facilitate sprint planning.

What is the best way to estimate effort levels for GitHub issues during triage?

Estimating effort levels for GitHub issues during triage is done by categorizing them into predefined sizes (XS, S, M, L, XL). This effort estimation framework supports sprint planning by balancing workload based on issue complexity.

Does GitHub issue triage require specific repository permissions to assign labels?

GitHub issue triage requires access to the target GitHub repository and relevant permissions. These access rights are necessary to utilize the GitHub API for automated label assignment and issue tracking.

Can I detect and link duplicate GitHub issues to avoid redundant development work?

Detecting and linking duplicate GitHub issues is possible during the triage process. Identifying duplicates prevents redundant work by consolidating similar reports and linking them together for streamlined development.

How does structured label taxonomy improve GitHub issue management?

A structured label taxonomy improves GitHub issue management by assigning predefined labels for type, priority, effort, and status. This ensures issues are appropriately categorized for further discussion and development.

What is included in a GitHub issue triage report for sprint planning?

A GitHub issue triage report for sprint planning includes classified issues with assigned priorities, effort estimations, and duplicate detection results. This comprehensive report ensures appropriately labeled issues are ready for development.