skills.rest
easonlao
easonlaoCOMMUNITY
Explore all skills by this author →
GitHub

bug-triage

Prioritize and assign open QA bugs by severity and urgency.

Updated Apr 25, 2026
Search Tags:#qa#report generation#sprint planning#trend analysis#regression detection#bug triage#severity vs priority
One-click install
npx skills add https://github.com/easonlao/jiazi-game --skill bug-triage-easonlao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-triage
Source: https://github.com/easonlao/jiazi-game/tree/main/.claude/skills/bug-triage
Command: npx skills add https://github.com/easonlao/jiazi-game --skill bug-triage-easonlao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns an unstructured open bug backlog into a prioritized, sprint-assigned action list while surfacing severity/priority tradeoffs and systemic issue trends.

Core Features & Use Cases

  • Severity and Priority Classification: Recommends objective severity (S1–S4) and team-oriented priority (P1–P4) to clarify impact versus urgency.
  • Mode-Based Triage: Supports sprint-scoped assignment, full backlog re-triage, and trend-only readouts.
  • Systemic Trend Detection: Flags patterns like clusters of bugs from the same system or regressions in completed stories to reduce repeated failures.
  • Triage Reporting: Produces a dated markdown report saved to production/qa/bug-triage-[date].md.

Quick Start

Run bug triage in sprint mode to re-prioritize current open bugs and assign appropriate ones to the active sprint, including systemic trend notes, by asking: /bug-triage 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 a QA bug backlog for an upcoming sprint?▼

Bug triage for sprint planning evaluates open production QA bugs by comparing impact severity against fix urgency, generating a sprint-assigned action list. The process reads bug files and sprint context to output a dated markdown triage report.

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

In bug triage, severity measures objective system impact ranging from S1 to S4, while priority determines team-oriented fix urgency from P1 to P4. Classifying both metrics clarifies the tradeoff between a bug's technical impact and its business urgency.

How can I detect systemic trends and regressions in completed stories during bug triage?▼

Systemic trend detection during bug triage flags patterns like clusters of bugs originating from the same system and regressions found in completed stories. This analysis reduces repeated failures by surfacing underlying issue trends within the open bug backlog.

Can I re-prioritize my full bug backlog or do I need to wait for sprint planning?▼

You can re-prioritize a full bug backlog anytime using mode-based triage, which supports full backlog re-triage, sprint-scoped assignment, and trend-only readouts. This allows post-QA filing re-prioritization whenever bug counts grow without waiting for sprint planning.

What format does the generated bug triage report use and where is it saved?▼

The generated bug triage report uses a markdown format and is saved to production/qa/bug-triage-[date].md. This dated report includes prioritized assignments, severity versus priority tradeoffs, and systemic trend insights with approval-based gating for output.

Related Skills

Explore More Software Engineering Skills→
imgamerimgamer

bug-triage

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

Community
Advanced
nuoyanruoshuinuoyanruoshui
47

bug-triage

Prioritize open software bugs into sprint assignments and triage reports.

Community
Advanced
brand6brand6

bug-triage

Triage open bugs by re-evaluating severity, priority, and sprint alignment.

Community
Intermediate
OreStudioOreStudio
25

agile-product-owner

Create and prioritize user stories across ORE Studio sprint and product backlogs.

Official
Basic