triage

Classify, enrich, prioritize, and manage GitHub issues labeled status:needs-triage.

25|5|Updated May 9, 2026
One-click install
npx skills add https://github.com/kamp-us/phoenix --skill triage-kamp-us
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/kamp-us/phoenix/tree/main/claude-plugins/kampus-pipeline/skills/triage
Command: npx skills add https://github.com/kamp-us/phoenix --skill triage-kamp-us

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh-api, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the triage process for GitHub issues, improving the quality and organization of your issue queue by efficiently classifying, enriching, prioritizing, and managing GitHub issues labeled status:needs-triage.

Core Features & Use Cases

  • Automated Issue Classification: Automatically classify issues into bug, feature, chore, decision, investigation, or epic types based on their content.
  • Enrichment and Rewrite: Rewrite and enrich issue descriptions to provide clearer, actionable information.
  • Priority Assignment: Assign priorities (p0, p1, p2) to issues based on their importance and urgency.
  • Issue Splitting: Split bundled reports into individual issues for better organization and management.
  • Issue Management: Close issues as not planned if they are unsalvageable and provide an audit trail.
  • Use Case: Integrate this Skill into your CI/CD pipeline to streamline the issue triage process and improve issue quality.

Quick Start

Trigger the triage Skill by typing "triage the queue" or "process needs-triage".

Frequently Asked Questions about triage

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

FAQPage Schema
How do I automate GitHub issue triage for a large backlog?

Automated GitHub issue triage classifies issues into types like bug or feature, assigns priorities, and rewrites descriptions for clarity. It processes issues labeled `status:needs-triage` to improve overall backlog organization.

What is the best way to split bundled GitHub issues into individual tickets?

Splitting bundled GitHub issues separates multiple reports within a single ticket into distinct, manageable items. This automation identifies bundled reports and creates individual issues to improve tracking and resolution.

How do I automatically assign priorities to GitHub issues based on urgency?

Automatic priority assignment evaluates issue importance and urgency to label them p0, p1, or p2. This ensures critical bugs and features are addressed first during the GitHub issue triage process.

Do I need the gh-api dependency to automate issue management on GitHub?

Yes, the gh-api dependency is required to interact with GitHub's API for issue management. It enables the automated triage workflows to read, update, and close issues directly within your repository.

Can I integrate issue triage automation into a CI/CD pipeline?

Yes, you can integrate this triage automation into your CI/CD pipeline to streamline issue processing. Triggering it with commands like "triage the queue" processes needs-triage labels automatically during workflows.

How does automated triage handle unsalvageable GitHub issues?

Automated triage closes unsalvageable GitHub issues as not planned while providing an audit trail. This keeps the issue queue clean by removing reports that lack actionable information or context.