triage-issues

Name: triage-issues
Availability: InStock
Author: TalonT

Analyze GitHub issues and generate a sequenced implementation plan with batches.

5|1|Updated Feb 18, 2026

Search Tags:#automation #workflow #planning #github #prioritization #issues #triage

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complex and time-consuming process of analyzing, classifying, and sequencing GitHub issues, transforming a chaotic backlog into an actionable implementation plan.

Core Features & Use Cases

Automated Issue Classification: Assigns issues to implementation or remediation recipes with rationale.
Batch Creation: Groups issues into parallel execution batches based on dependencies and complexity.
Dependency Analysis: Identifies conflicts and ordering requirements between issues.
Use Case: Before starting a new development sprint, use this skill to automatically triage all open bugs and feature requests, creating ordered batches of work ready for the development team.

Quick Start

Use the triage-issues skill to analyze and plan the order of all open GitHub issues in the current repository.

Frequently Asked Questions about triage-issues

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

FAQPage Schema

How do I prioritize and sequence GitHub issues for a sprint?▼

GitHub issue triage works by classifying issues as remediation or implementation, identifying affected file paths, building a conflict graph, and grouping issues into parallel execution batches to form a sequenced implementation plan.

What is the best way to group GitHub issues into parallel work batches?▼

The best way to group GitHub issues is by building a conflict graph from affected file paths and dependencies, then using a greedy partitioning approach to create ordered batches of non-conflicting work.

Can I use this to separate broken behavior bugs from missing feature requests?▼

Yes, the skill classifies issues into remediation or implementation recipes based on whether existing behavior is broken or missing, providing structured rationale for each classification to separate bugs from feature requests.

Does the issue sequencing support dry runs and batch size limits?▼

Yes, the skill supports optional arguments for batch size limits and dry runs, allowing you to safely preview the generated implementation plan and control the number of issues partitioned into each parallel batch.

How do I collapse related GitHub issues during backlog triage?▼

You can collapse related GitHub issues by enabling the optional collapse argument, which groups related issues together and enriches them with structured requirements during the triage and batch partitioning process.