triage

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

Updated May 21, 2026
One-click install
npx skills add https://github.com/sunzcdev/archon-dev-team --skill triage-sunzcdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/sunzcdev/archon-dev-team/tree/main/.claude/skills/triage
Command: npx skills add https://github.com/sunzcdev/archon-dev-team --skill triage-sunzcdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents inconsistent, slow, and incomplete GitHub issue labeling by turning triage into a structured, repeatable workflow that applies the right type, effort, priority, and area labels.

Core Features & Use Cases

  • Deterministic issue triage: Applies labels using a clear scope mechanism (unlabeled, unlabeled-only, all issues, or a specific/range of issue numbers).
  • Isolated execution with a specialized agent: Runs triage in a forked isolated context and delegates classification to a purpose-built triage agent.
  • Label validation guardrails: Uses a validation hook to ensure label category completeness before label edits are finalized.
  • Safety and hygiene: Disables automatic model invocation and restricts tools to GitHub CLI plus read-only repository access.

Quick Start

Ask your agent to run triage for unlabeled issues with no arguments: "Use the triage skill to label all currently unlabeled open GitHub issues in this repository."

Frequently Asked Questions about triage

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

FAQPage Schema
How do I automatically apply consistent labels to GitHub issues?

Automating GitHub issue triage applies type, effort, priority, and area labels consistently. It uses a validation hook to ensure label category completeness before finalizing edits, preventing incomplete or inaccurate categorization across your repository.

Can I triage specific GitHub issue numbers instead of all open issues?

Yes, GitHub issue triage operates on selectable scopes. You can target unlabeled-only issues, all open issues, or specific issue numbers and ranges in active repositories to precisely control which items get processed.

What is the best way to estimate effort and priority for GitHub issues?

Effort estimation and priority assignment for GitHub issues are handled by a specialized triage agent. This agent runs in an isolated forked execution context, applying deterministic labels based on your repository's established taxonomy.

Does automated issue triage work safely with restricted repository permissions?

Yes, automated issue triage enforces safety by running in isolated forked execution and restricting tools to GitHub CLI read-only access. It only performs label edits via allowed patterns and disables automatic model invocation.

Why does my GitHub issue triage workflow apply inconsistent labels?

Inconsistent GitHub issue labeling often occurs without enforced taxonomy rules. This triage workflow solves the problem by using label-completeness validation guardrails to ensure type, effort, priority, and area labels are applied correctly.