triage

Apply type, effort, priority, and area labels to GitHub issues.

Updated May 13, 2026

Search Tags:#workflow automation #github #governance #effort estimation #priority #issue triage #labeling

Ready to run

npx skills add https://github.com/cliffthelin/AXiomEngine --skill triage-cliffthelin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/cliffthelin/AXiomEngine/tree/main/archon/.claude/skills/triage
Command: npx skills add https://github.com/cliffthelin/AXiomEngine --skill triage-cliffthelin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces the time and inconsistency involved in labeling GitHub issues by automatically applying the correct type, effort, priority, and area labels.

Core Features & Use Cases

Label-driven issue triage: Classifies each issue into one type, one effort level, one priority, and one or more areas by reading the title and full body.
Scope-controlled triaging: Supports triaging only unlabeled issues by default, or switching to unlabeled, all, a single issue number, or an inclusive range.
Safety-first validation and hygiene: Runs in a forked isolated context and delegates label logic to a triage agent that validates label completeness before edits are applied.

Quick Start

Ask the assistant to run triage for the unlabeled issues in the repository.

Frequently Asked Questions about triage

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

FAQPage Schema

How do I automatically triage and label GitHub issues?▼

To automatically triage GitHub issues, this Skill reads the title and full body of each issue to apply consistent type, effort, priority, and area labels based on your repository's existing taxonomy.

Can I triage a specific range of GitHub issues instead of the whole backlog?▼

Yes, you can triage a specific range of GitHub issues by configuring the scope to process only unlabeled issues, all issues, a single issue number, or an inclusive range of issue numbers.

How does effort estimation work when triaging GitHub issues?▼

Effort estimation during GitHub issue triage works by analyzing the title and full body content to assign a corresponding effort label, alongside type, priority, and area classifications.

Does this tool require an existing label taxonomy to prioritize GitHub issues?▼

Yes, prioritizing GitHub issues requires your repository to have an existing label taxonomy, as the Skill retrieves current labels live and validates label completeness before applying edits.

What is the safest way to groom a backlog of unlabeled GitHub issues?▼

The safest way to groom unlabeled GitHub issues is using a forked isolated context that validates label completeness through a triage agent before any GitHub issue edits are actually applied.

Can I inspect my codebase during GitHub issue triage for better labeling context?▼

Yes, optional codebase inspection is supported during GitHub issue triage to provide additional context, ensuring the applied type, effort, priority, and area labels are accurate.