triage-taxonomy

Match bug descriptions to BugCard and BugFull history and map symptoms to taxonomy tags.

15|5|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/haolange/RDC-Agent-Frameworks --skill triage-taxonomy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-taxonomy
Source: https://github.com/haolange/RDC-Agent-Frameworks/tree/main/debugger/platforms/claude-code/.claude/skills/triage-taxonomy
Command: npx skills add https://github.com/haolange/RDC-Agent-Frameworks --skill triage-taxonomy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a specialist triage capability that matches incoming bug descriptions to historical BugCard/BugFull records, normalizes symptoms and triggers into taxonomy tags, and surfaces candidate standard operating procedures and investigation directions so that responders can act faster and more consistently.

Core Features & Use Cases

  • History Matching: Compare a new bug report against BugCard and BugFull histories to find precedent cases and relevant metadata.
  • Taxonomy Mapping: Convert free-text symptoms and triggers into normalized tags used across the debugging framework.
  • SOP Recommendation & Exploration Guidance: Suggest candidate SOPs and prioritized next-step exploration directions for the main agent to follow.
  • Use Case: When an rdc-debugger agent dispatches a triage task during incident handling, use this skill to produce structured tags, linkable precedent cases, and recommended investigative actions to accelerate resolution.

Quick Start

Ask the triage-taxonomy specialist to analyze the bug description and return normalized tags, recommended SOP candidates, and prioritized exploration directions.

Frequently Asked Questions about triage-taxonomy

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

FAQPage Schema
How do I classify bug symptoms into normalized taxonomy tags during incident analysis?

Bug triage maps free-text symptoms and triggers from bug descriptions against BugCard and BugFull histories to generate normalized taxonomy tags. It matches incoming reports to precedent cases, enabling consistent classification across incident-analysis workflows.

What is the best way to recommend standard operating procedures for a new bug report?

Triage taxonomy suggests candidate SOPs by matching new bug descriptions against historical BugCard and BugFull records. It surfaces prioritized next-step exploration directions so responders can act faster and more consistently during incident handling.

How does bug triage matching work with historical debugging records?

Bug triage compares a new bug report against BugCard and BugFull histories to find precedent cases and relevant metadata. This history matching converts free-text symptoms into normalized tags used across the debugging framework.

Can I use triage taxonomy for agent-driven debugging workflows with multi-agent orchestration?

Yes, triage taxonomy applies to internal agent-driven debugging workflows where rdc-debugger dispatches triage tasks. It requires access to platform-local runtime artifacts, broker-mediated live access controls, and adherence to staged_handoff multi-agent orchestration policies.

Do I need platform-local runtime artifacts to perform incident classification?

Yes, incident classification requires access to platform-local runtime artifacts and broker-mediated live access controls. These components are necessary for the triage taxonomy specialist to map symptoms and return recommended investigative actions.

Why use taxonomy mapping instead of manual bug triage during incident handling?

Taxonomy mapping normalizes free-text symptoms and triggers into standardized tags, linking precedent cases and SOP candidates automatically. This accelerates resolution and ensures consistency compared to manual triage, providing structured tags and prioritized exploration directions.