issue-classification

Name: issue-classification
Availability: InStock
Author: fullsend-ai

Classify GitHub issues into exact workstream categories with confidence thresholds.

1|6|Updated Mar 26, 2026

Search Tags:#workflow #github #comments #issues #classification #triage #labels

Ready to run

npx skills add https://github.com/fullsend-ai/.fullsend --skill issue-classification

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue-classification
Source: https://github.com/fullsend-ai/.fullsend/tree/main/customized/skills/issue-classification
Command: npx skills add https://github.com/fullsend-ai/.fullsend --skill issue-classification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps an agent turn messy GitHub issues into exact project categories so teams can route work consistently and avoid manual triage.

Core Features & Use Cases

Reads the authoritative categories document and extracts the valid category names for exact matching.
Screens open issues by title, labels, body, and comments to decide which items deserve deeper review.
Supports both single-issue and batch classification workflows, while skipping issues that are already classified on the project board.
Use it when a repository needs reliable issue triage, category assignment, and concise reasoning for each decision.

Quick Start

Use this skill to classify the relevant GitHub issues in the target repository according to the provided categories and return a JSON result with reasoning and confidence.

Frequently Asked Questions about issue-classification

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

FAQPage Schema

How do I automatically classify GitHub issues into project categories?▼

GitHub issue triage screens open issues by title, body, labels, and comments, then evaluates content against a categories document to assign exact workstream categories and return JSON results with reasoning and confidence scores.

How does issue triage handle issues that are already labeled on a project board?▼

Batch issue triage workflows skip issues that already have classification labels on the GitHub project board, preventing redundant processing and focusing evaluation only on open issues lacking exact category assignments.

Can I batch classify open GitHub issues or do I need to process them one by one?▼

Batch issue classification is fully supported. The workflow processes multiple open GitHub issues simultaneously, screening titles, labels, bodies, comments, and project board state to apply exact category matches across all items in a single run.

What happens when issue content is ambiguous and lacks a clear category match?▼

When GitHub issue content is ambiguous, the classification workflow applies confidence thresholds and outputs null. This prevents unreliable category routing and ensures only issues with exact category matches receive assignments.

Does GitHub issue classification require a predefined list of categories to match against?▼

Yes, issue classification requires a predefined categories document. The workflow reads this authoritative source, extracts valid category names, and requires exact matching against that list before assigning workstream categories to open issues.

Why does GitHub issue triage return a null output for certain issues?▼

Triage returns null output when issue content is ambiguous and cannot meet confidence thresholds for exact category matching. This prevents false positives and ensures only issues with clear, classifiable signals receive workstream assignments.