bug-triage

Reprioritize open bug backlogs by comparing severity to urgency and assign issues to sprint targets.

72|7|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill bug-triage-striderza
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-triage
Source: https://github.com/striderZA/OpenCodeGameStudios/tree/main/.opencode/skills/bug-triage
Command: npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill bug-triage-striderza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns a growing set of open production/QA bugs into a clear, sprint-ready plan by re-evaluating priority against severity, preventing critical issues from being missed, and surfacing systemic trends.

Core Features & Use Cases

  • Severity vs. Priority Classification: Separates objective impact (severity S1–S4) from urgency (priority P1–P4) so the team triages consistently.
  • Sprint Assignment With Capacity Awareness: Assigns P1/P2 bugs to the current sprint (or next estimate) while flagging priority overflow for sprint owners to decide.
  • Systemic Trend Detection & Readout: Highlights repeated issues in the same system/story and generates a report with volume, hot spots, regressions, and age analysis.

Quick Start

Run the command bug-triage sprint to triage the open bug backlog against the current sprint and produce a prioritized, assigned report.

Frequently Asked Questions about bug-triage

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

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

Prioritize a QA bug backlog by comparing objective severity impact against fix urgency priority. This separates S1–S4 impact from P1–P4 urgency, assigning critical issues to the current sprint while flagging overflow for owners to review.

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

Severity in bug triage measures objective system impact on a scale of S1–S4, while priority measures fix urgency on a scale of P1–P4. Separating these metrics ensures consistent triage and prevents critical issues from being missed during sprint planning.

How do I assign production bugs to the current sprint automatically?

Assign production bugs to the current sprint by evaluating priority against severity and sprint capacity. The process allocates P1 and P2 issues to active sprints, flags priority overflow, and outputs a prioritized report for sprint owners.

Can I detect systemic regression trends in an open bug backlog?

Detect systemic regression trends in an open bug backlog by analyzing issue volume, hot spots, and age. The triage process highlights repeated issues within the same system or story and generates a readout for sprint planning.

When should I run a bug triage workflow on production issues?

Run a bug triage workflow on production issues at sprint start, after QA filing, or whenever the open bug count grows beyond a manageable threshold. This reprioritizes the backlog against the latest sprint context and severity references.

Does bug triage automatically write sprint assignments to files?

Bug triage does not automatically write sprint assignments to files. It produces a triage report and gates all writes behind explicit user approval, ensuring sprint owners review priority overflow and capacity allocation before committing changes.