bug-triage

Reconcile severity and priority to reprioritize and assign open bug backlog items.

Updated Dec 22, 2024
One-click install
npx skills add https://github.com/imgamer/AILearn --skill bug-triage-imgamer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-triage
Source: https://github.com/imgamer/AILearn/tree/main/game-studios/Claude-Code-Game-Studios-e375f/.claude/skills/bug-triage
Command: npx skills add https://github.com/imgamer/AILearn --skill bug-triage-imgamer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents production/QA bug backlogs from becoming unmanageable by re-evaluating severity and priority, assigning actionable items to sprints, and highlighting systemic quality problems.

Core Features & Use Cases

  • Backlog triage with severity vs. priority: Reclassifies issues using S1–S4 impact and P1–P4 urgency to produce an actionable plan rather than a flat list.
  • Sprint-aware assignment: Reads the most recently modified sprint plan to assign eligible P1/P2 bugs while avoiding auto-assignment when capacity is full.
  • Systemic trend detection: Flags patterns such as multiple high-impact bugs from the same system and regressions in previously completed stories.
  • Report generation gate: Produces a structured triage report and requests approval before writing the output file.

Quick Start

Run the bug-triage skill in sprint mode to prioritize open production/QA bugs and generate a sprint-assigned report for the current sprint context.

Frequently Asked Questions about bug-triage

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

FAQPage Schema
How do I triage a bug backlog for sprint planning?

Bug triage reprioritizes open production and QA bugs by reconciling severity and priority, classifying each issue with deviation checks, and assigning eligible items to the current sprint. It generates an approval-gated sprint-ready triage report.

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

Bug triage maps severity to S1–S4 impact levels and priority to P1–P4 urgency. It reconciles these two dimensions to reclassify flat bug lists into an actionable, sprint-aware execution plan rather than treating them as identical values.

How does bug triage handle systemic hot spots and regression detection?

Bug triage detects systemic trends by flagging patterns such as multiple high-impact bugs originating from the same system and identifying regressions in previously completed stories, highlighting broader quality problems in the generated report.

Can I auto-assign P1 and P2 bugs when sprint capacity is full?

Bug triage reads the most recently modified sprint plan to assign eligible P1 and P2 bugs, but it specifically avoids auto-assignment when sprint capacity is already full, preventing over-allocation during sprint planning.

What file format is needed to run a bug backlog re-evaluation?

Bug triage requires reading bug backlog files via glob patterns to extract sprint context and severity references. It processes these inputs and generates an approval-gated write to a markdown file named bug-triage-[date].md.

When should I run a full backlog re-evaluation instead of sprint-start triage?

Run a full backlog re-evaluation when bug volume crosses a defined threshold, making the queue unmanageable. Sprint-start workflows and post-team QA bug updates are better suited for routine priority checks and sprint-aware assignment.