bug-triage

Classify open bugs by severity and priority, assign them to sprints, and generate a triage report.

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

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 every open bug report, re-evaluates severity versus priority, assigns fixes to sprints, and surfaces trends before they become release blockers. ## Core Features & Use Cases - Severity and priority classification: Rates each bug on S1-S4 severity and P1-P4 priority scales, then assigns P1/P2 bugs to the current or next sprint based on capacity. - Systemic trend detection: Flags hot-spot systems, regressions against completed stories, and aged high-severity bugs that represent accepted risk. - Structured triage report: Produces a Markdown report at production/qa/bug-triage-[date].md with summary tables, assignments, and recommended actions. - Use Case: At sprint start, run the triage to process 15 open bugs, assign the 4 P1 items to the current sprint, and discover that the rendering system has produced 3 bugs in one sprint, signaling a design quality issue. ## Quick Start Ask the AI to run bug triage in sprint mode against the open bugs in production/qa/bugs/ and produce 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 bug backlog before sprint planning?

Run the triage in sprint mode to read all open bug files, classify each by severity (S1-S4) and priority (P1-P4), and assign fixable bugs to the current sprint based on remaining capacity. The output is a Markdown triage report with assignments and recommended actions.

What is the difference between bug severity and priority?

Severity measures impact: S1 means crashes or data loss, S4 means cosmetic issues. Priority measures urgency: P1 means fix this sprint, P4 means deferred. The skill treats severity as objective and priority as a team decision presented as recommendations.

What bug file formats does the triage process read?

It reads individual Markdown bug reports in production/qa/bugs/ first, falls back to a consolidated bugs.md file, and as a last resort parses Bugs Found tables in QA plan files. If no bug files exist, it stops and reports rather than proceeding.

Can the triage detect systemic quality problems?

Yes. It flags patterns such as 3 or more bugs from the same system in one sprint, multiple S1/S2 bugs in a single story, and bugs filed against stories already marked complete, which indicate regressions requiring story reopening.

Does bug triage modify bug statuses automatically?

No. It never closes bugs or marks them Won't Fix without explicit user approval, never auto-assigns to a sprint at capacity, and asks for confirmation before writing the triage report to disk.