triage

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

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/RsultCoding/rca-archon --skill triage-rsultcoding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/RsultCoding/rca-archon/tree/main/.claude/skills/triage
Command: npx skills add https://github.com/RsultCoding/rca-archon --skill triage-rsultcoding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage GitHub issues by applying type, effort, priority, and area labels. Runs in an isolated context to avoid polluting the main conversation with issue details. Delegates to a specialized triage agent with label validation hooks.

Core Features & Use Cases

  • Context: fork — isolates triage runs from the main conversation to protect context cleanliness.
  • Agent delegation — uses a custom triage-agent to classify issues and apply labels.
  • Guardrails — a post-tool-use prompt hook validates that each label category (type, effort, priority, area) is present before edits.
  • Tools access — restricted to GitHub CLI read operations and codebase reads to enforce safety.

Quick Start

Invoke the triage skill on a single issue by using /triage <issue-number> to start the isolated triage workflow.

Frequently Asked Questions about triage

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

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

Automated GitHub issue triage applies type, effort, priority, and area labels using a specialized agent. It runs in an isolated context to analyze issues and enforce all four label categories before applying changes.

Can I triage multiple GitHub issues at once instead of one by one?

Yes, GitHub issue triage supports range-based workflows. You can process multiple open issues across repositories by specifying a scope argument, while single-issue triage is also available for targeted labeling.

What's the best way to keep my conversation context clean when managing GitHub issue labels?

Forked execution context isolates GitHub issue triage runs from the main conversation. This prevents issue details from polluting your context while the triage agent classifies and labels issues independently.

Does GitHub issue triage validate labels before applying them to repositories?

Yes, a post-tool-use hook validates GitHub issue labels before edits are committed. This guardrail enforces that type, effort, priority, and area categories are all present, ensuring complete issue classification.

What GitHub CLI permissions are needed for automated issue triage?

Automated issue triage restricts tool access to GitHub CLI read operations and codebase reads. This enforces safety by limiting permissions while the agent analyzes open issues to apply category labels.