bug-triage

Prioritize and assign open production QA bugs by severity, urgency, and sprint capacity.

1|Updated May 5, 2026
One-click install
npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill bug-triage-xganqaq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-triage
Source: https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios/tree/main/.claude/skills/bug-triage
Command: npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill bug-triage-xganqaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents game QA and sprint planning from stalling by turning an unstructured open-bug backlog into an actionable, priority-based plan tied to the current sprint’s scope and capacity.

Core Features & Use Cases

  • Severity vs. Priority Classification: Separates impact (S1–S4) from urgency (P1–P4) to make triage decisions that are consistent and reviewable.
  • Sprint-Aware Assignment: Assigns P1/P2 bugs to the appropriate sprint backlog in sprint mode while flagging “priority overflow” when capacity is tight.
  • Systemic Trend Detection: Detects repeated problem patterns (e.g., multiple bugs from the same system, regressions from completed stories) to surface quality issues early.
  • Readable Triage Report Output: Produces a dated report at production/qa/bug-triage-[date].md for team visibility and follow-through.

Quick Start

Run bug triage in sprint mode using the command /bug-triage sprint to prioritize the current open bug backlog and assign fixable items to the active sprint.

Frequently Asked Questions about bug-triage

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

FAQPage Schema
How do I prioritize bugs for sprint planning when the backlog is overflowing?

Bug triage resolves an overflowing backlog by evaluating severity impact and urgency priority to assign fixable items to the active sprint while flagging priority overflow when capacity is tight.

What is the difference between severity and priority in QA bug triage?

In bug triage, severity measures impact (S1–S4) while priority measures urgency (P1–P4), separating these dimensions to make consistent and reviewable triage decisions for sprint planning.

How do I detect systemic regressions and repeated problem patterns in a bug backlog?

Bug triage detects systemic trends by analyzing the open backlog for repeated problem patterns, such as regressions from completed stories or multiple bugs from the same system, to surface quality issues early.

Can I generate a dated triage report for my QA backlog automatically?

Yes, bug triage writes an approved dated triage report to production/qa/bug-triage-[date].md, providing team visibility and follow-through for your current open bug backlog.

How do I assign P1 and P2 bugs to a sprint backlog without exceeding capacity?

Bug triage assigns P1/P2 bugs to the appropriate sprint backlog in sprint mode and explicitly flags priority overflow, ensuring sprint capacity constraints are respected during planning.

Do I need a specific bug backlog file format to run a regression detection analysis?

Bug triage requires reading your existing bug backlog files to derive or apply severity definitions and detect systemic trends, operating directly on your unstructured open-bug backlog data.