issue-triage

Name: issue-triage
Availability: InStock
Author: chichex

Analyze GitHub issues against repository code and contracts to determine execution paths.

2|Updated Jul 13, 2026

Search Tags:#automation #workflow #planning #github #sdd #triage

Ready to run

npx skills add https://github.com/chichex/skills --skill issue-triage-chichex

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue-triage
Source: https://github.com/chichex/skills/tree/main/codex/issue-triage
Command: npx skills add https://github.com/chichex/skills --skill issue-triage-chichex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the ambiguity and manual overhead of managing GitHub issues by providing a structured, evidence-based framework to decide whether to reject, grill, specify, or execute a task.

Core Features & Use Cases

Automated Triage: Analyzes issue bodies, code, and repository contracts to determine the most reliable path forward.
Canonicalization: Automatically combines multiple related issues into a single, cohesive unit of work to prevent fragmentation.
Safety Gates: Enforces strict checks before allowing direct implementation, ensuring that only well-defined, low-risk tasks proceed to quick-run.

Quick Start

Invoke the issue-triage skill by passing the numbers of the issues you wish to analyze from your current repository.

Frequently Asked Questions about issue-triage

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

FAQPage Schema

How do I automate GitHub issue triage to decide whether to execute or reject a task?▼

Automated GitHub issue triage analyzes issue bodies against repository code and contracts to determine the optimal execution path, rejecting or executing tasks based on evidence. This eliminates manual overhead by enforcing strict safety gates before implementation.

What is evidence-based issue routing in software development workflows?▼

Evidence-based issue routing evaluates GitHub issues against existing code, tests, and project contracts to define scope and validate technical feasibility. It ensures deterministic task planning by applying strict checks before any implementation begins.

How do I combine multiple related GitHub issues into a single unit of work?▼

Combining multiple related GitHub issues uses a canonicalization process that merges fragmented tickets into a cohesive unit of work. This prevents scattered efforts and ensures tasks are prioritized with proper dependency tracking.

Does automated issue triage work without defining project contracts and repository tests?▼

Automated issue triage requires repository code, tests, and project contracts to validate technical feasibility and enforce safety gates. Without these inputs, it cannot determine the optimal execution path or ensure low-risk tasks proceed to implementation.

What is the best way to prioritize GitHub issues and track dependencies for task planning?▼

Prioritizing GitHub issues and tracking dependencies is best handled by analyzing issue bodies against repository contracts to map out a deterministic execution path. This approach ensures only well-defined, low-risk tasks proceed to automated PR generation.

Why should I not use automated triage for poorly defined GitHub issues?▼

Automated triage should not be used for poorly defined GitHub issues because strict safety gates enforce checks before allowing direct implementation. Only well-defined, low-risk tasks that pass technical validation against repository contracts proceed to quick-run.