bug-triage

Classifies open bug reports by severity and priority, assigns them to sprints, and generates a triage report.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill bug-triage-claretagrapelike32
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-triage
Source: https://github.com/claretagrapelike32/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/bug-triage
Command: npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill bug-triage-claretagrapelike32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Open bug backlogs grow without consistent prioritization, causing critical defects to be lost between sprints and systemic quality issues to go unnoticed. This Skill reads all open bugs, re-evaluates severity versus priority, assigns fixes to sprints, and surfaces trends in a structured triage report. ## Core Features & Use Cases - Severity and Priority Classification: Scores each bug on S1-S4 severity and P1-P4 priority scales, distinguishing impact from urgency. - Sprint Assignment: Assigns P1/P2 bugs to the current sprint based on capacity, flagging overflow instead of overloading the sprint. - Trend and Regression Analysis: Detects systemic hot spots, aged high-severity bugs, and regressions against completed stories. - Use Case: At sprint start, run the triage to process 15 open bugs in production/qa/bugs/, assign the 4 critical ones to the current sprint, and produce a report highlighting that the rendering system has become a quality hot spot. ## Quick Start Ask the AI to run bug triage in sprint mode against the open bugs in production/qa/bugs/ and generate a prioritized triage report.

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 backlog of open bugs before a sprint?

Run the triage in sprint mode to read all bug files in production/qa/bugs/, classify each by severity and priority, and assign P1/P2 bugs to the current sprint based on remaining capacity. The output is a structured triage report with recommended actions.

What is the difference between bug severity and priority?

Severity measures impact, from S1 critical crashes to S4 cosmetic issues, while priority measures fix urgency, from P1 fix-this-sprint to P4 won't-fix. The skill treats severity as objective and priority as a team decision presented as recommendations.

Can bug triage detect systemic quality problems?

Yes, it flags patterns such as three or more bugs from the same system in one sprint, multiple high-severity bugs in a single story, and regressions filed against completed stories. These appear in the Systemic Issues Flagged section of the report.

What happens if no bug files are found?

The skill stops and reports that no bug files exist in production/qa/bugs/, suggesting you adjust the glob pattern if bugs are tracked elsewhere. It does not proceed with an empty backlog.

Does bug triage modify bug files automatically?

No, it presents the triage report in conversation first and writes it to production/qa/bug-triage-[date].md only after your approval. It also never closes bugs or marks them Won't Fix without explicit user confirmation.