bug-triage

Classify markdown bug reports and assign P1/P2 issues to sprints.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill bug-triage-polsegu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-triage
Source: https://github.com/polsegu/Claude-Code-Game-Dev/tree/main/.claude/skills/bug-triage
Command: npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill bug-triage-polsegu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual, error-prone work of reading disparate bug reports, re-evaluating severity versus priority, and deciding which fixes belong in the current sprint versus the backlog so that critical issues are surfaced and assigned reliably.

Core Features & Use Cases

  • Automated discovery and loading of markdown bug reports and sprint context from production/qa/bugs and production/sprints to create a single view of open issues.
  • Severity and priority classification with rules for assigning P1/P2 bugs to sprints while respecting capacity and flagging overflow or regressions.
  • Trend analysis and reporting that highlights system hot spots, aged high-severity issues, and generates a human-reviewable triage report for sprint planning or QA gating.

Quick Start

Run /bug-triage sprint to analyze open bugs, classify severity and priority, assign P1/P2 issues to the current sprint when capacity allows, and generate a triage report for review.

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 bug backlog for sprint planning?

Bug triage automates sprint planning by classifying severity and priority of open issues, assigning P1/P2 bugs to sprints while respecting capacity, and generating a markdown triage report ready for review.

What is the best way to classify bug severity and priority for a triage report?

The best way to classify bug severity and priority is to apply automated rules that evaluate markdown bug reports, detect systemic trends, flag regressions, and generate a human-reviewable triage report for sprint planning.

How do I assign P1 and P2 bugs to sprints without exceeding capacity?

You assign P1 and P2 bugs without exceeding capacity by evaluating open issues against sprint capacity limits, assigning feasible critical fixes, and flagging overflow or regressions for backlog management.

Does bug triage work with markdown bug reports and sprint files?

Yes, bug triage works with markdown bug reports and sprint files by automatically discovering and loading them from production directories to create a single view of open issues for severity classification and sprint assignment.

When should I run a bug triage report after QA runs?

You should run a bug triage report after QA runs, at sprint start, or when open bug counts exceed the re-prioritization threshold, ensuring critical issues are surfaced and assigned reliably for planning or QA gating.

Can I detect systemic bug trends and hot spots in my backlog?

Yes, you can detect systemic bug trends and hot spots in your backlog through trend analysis that highlights aged high-severity issues and system hot spots, producing a markdown triage report for sprint planning and QA gating.