How does the skill handle issues without labels?

If labels are missing, the skill falls back to analyzing title patterns like 'fix:' or 'feat:'. If neither is present, it defaults to /feature with a low confidence rating.

What is the primary benefit of using this skill in a workflow?

It allows AI agents to automatically decide which development template or branch strategy to use without manual intervention from a human manager.

Is a specific CLI tool required to use this skill?

While a CLI command is planned, the current version uses built-in local logic to process issue JSON data independently.

What data is required for the classification to work?

The skill requires a valid issue_json parameter containing at least the title or labels of the issue being analyzed.

What work types does the Issue Classifier support?

It classifies issues into four distinct types: /bug (defects), /feature (new functionality), /chore (maintenance/refactoring), and /patch (critical hotfixes).

Issue Classifier

Name: Issue Classifier
Author: fractary

byfractary

•

Collaboration Tools

Categorizes development tasks automatically by analyzing issue metadata such as labels and title patterns.

About

The Issue Classifier skill optimizes project management by automatically determining the work type of a task from its metadata. By evaluating labels and title prefixes (like fix, feat, or chore) within an issue's JSON data, it classifies tasks into four categories: /bug, /feature, /chore, or /patch. This skill is a foundational component for automated workflows, ensuring that the correct development templates and logic are applied based on the specific nature of the work being performed.

Key Features

2 GitHub stars
Fallback logic to ensure continuous workflow progress
Confidence level scoring for every classification result
Automated classification into bug, feature, chore, or patch types
Rule-based analysis of issue labels and title prefixes
Integration-ready JSON output for work-manager agents

Use Cases

Standardizing issue categorization across large-scale software projects
Filtering and prioritizing high-urgency patches and critical bug fixes
Automating the selection of workflow templates in developer pipelines

About

Key Features

2 GitHub stars
Fallback logic to ensure continuous workflow progress
Confidence level scoring for every classification result
Automated classification into bug, feature, chore, or patch types
Rule-based analysis of issue labels and title prefixes
Integration-ready JSON output for work-manager agents

Use Cases

Standardizing issue categorization across large-scale software projects
Filtering and prioritizing high-urgency patches and critical bug fixes
Automating the selection of workflow templates in developer pipelines