issue-splitter

Name: issue-splitter
Availability: InStock
Author: TalonT

Analyze GitHub issues for mixed concerns and create labeled sub-issues with cross-references.

5|1|Updated Feb 18, 2026

Search Tags:#github #decomposition #issues #triage #feature request #bug tracking

Ready to run

npx skills add https://github.com/TalonT-Org/AutoSkillit --skill issue-splitter-talont-org

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue-splitter
Source: https://github.com/TalonT-Org/AutoSkillit/tree/main/src/autoskillit/skills/issue-splitter
Command: npx skills add https://github.com/TalonT-Org/AutoSkillit --skill issue-splitter-talont-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill tackles GitHub issues that bundle multiple distinct requests or problems, making them hard to track and resolve. It automatically identifies these separate concerns and creates new, focused sub-issues.

Core Features & Use Cases

Concern Identification: Analyzes issue titles and bodies to find separate bugs, feature requests, or investigations.
Sub-issue Creation: Generates new GitHub issues for each identified concern.
Cross-referencing: Links new sub-issues back to the original parent issue and labels them appropriately.
Use Case: A single GitHub issue reports a UI bug, requests a new feature, and asks for documentation clarification. This Skill splits it into three separate, actionable issues, each tagged for its specific resolution path.

Quick Start

Use the issue-splitter skill to analyze GitHub issue number 123 in the current repository.

Frequently Asked Questions about issue-splitter

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

FAQPage Schema

How do I split a GitHub issue that contains multiple bug reports and feature requests?▼

The issue-splitter analyzes GitHub issues for mixed concerns by evaluating titles and bodies to identify separate bugs or feature requests, then generates focused sub-issues with cross-references back to the parent.

When should I decompose GitHub issues during triage workflows?▼

You should decompose GitHub issues during triage as a pre-classification step when an issue bundles mixed concerns, making it hard to track and resolve by creating focused sub-issues for each distinct problem.

Can I automatically label and cross-reference sub-issues created from a parent GitHub issue?▼

Yes, when creating new GitHub issues for identified concerns, the issue-splitter automatically applies relevant labels and adds tracking comments to the parent issue to cross-reference the generated sub-issues.

What is the best way to triage a GitHub issue reporting a UI bug, a feature request, and documentation clarification together?▼

The best way to triage a mixed GitHub issue is to use an automated decomposition tool that splits it into separate, actionable issues, each tagged for its specific resolution path like bug tracking or feature requests.

Does the issue-splitter require any specific dependencies to analyze GitHub issues?▼

No specific dependencies are required to analyze GitHub issues for mixed concerns, as the issue-splitter operates directly by reading issue titles and bodies to identify separate requests or problems.