bug-triage

Process open bug reports into prioritized, sprint-assigned markdown triage reports.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nevesb/idol-agency-maker --skill bug-triage-nevesb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-triage
Source: https://github.com/nevesb/idol-agency-maker/tree/main/.claude/skills/bug-triage
Command: npx skills add https://github.com/nevesb/idol-agency-maker --skill bug-triage-nevesb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns an unorganized bug backlog into a prioritized, actionable triage report so teams can assign work to sprints, reduce regression risk, and surface systemic quality issues before release.

Core Features & Use Cases

  • Backlog discovery: Glob and read individual or consolidated bug reports from production/qa/bugs to build the input set.
  • Classification: Infer or extract severity (S1–S4) and recommend priority (P1–P4) with rationale.
  • Assignment & gating: Assign P1/P2 issues to the current or next sprint based on sprint capacity and flag overflow or required reopens.
  • Trend analysis: Produce volume, hot spot, age, and regression metrics to identify systemic problems.
  • Report generation: Produce a markdown triage report saved as production/qa/bug-triage-[date].md and follow collaborative protocols before writing.

Quick Start

Run the triage against the current backlog and produce a sprint-assigned report by invoking the skill with a mode, for example: /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 bug backlog for sprint planning?▼

Bug triage prioritizes an unorganized bug backlog by classifying severity (S1–S4) and recommending priority (P1–P4) with rationale. It assigns P1/P2 issues to sprints based on capacity and generates a markdown triage report for sprint planning.

What's the best way to flag regressions in QA bug reports?▼

To flag regressions in QA bug reports, the triage process analyzes open bug files from production/qa/bugs and produces volume, hot spot, age, and regression metrics. This surfaces systemic quality issues and identifies regressions in the final markdown report.

How do I assign bugs to sprints without exceeding capacity?▼

Bug triage assigns P1 and P2 issues to the current or next sprint by evaluating sprint capacity context from production/sprints/. It automatically flags capacity overflow or required reopens, ensuring sprint assignments remain realistic and gated by available resources.

Can I use bug triage for production and QA bug backlogs?▼

Yes, bug triage applies to both production and QA bug backlogs. It discovers bug reports from the production/qa/bugs directory and processes them during sprint starts or when bug volume increases to re-evaluate severity, priority, and assignment.

What file formats and inputs are needed for bug triage?▼

Bug triage requires read access to open bug reports in markdown format under production/qa/bugs/*.md, sprint context files from production/sprints/, and optional severity references in .claude/docs to generate a markdown triage report.

When should I run bug triage during the development cycle?▼

Run bug triage during sprint starts to assign prioritized work, or whenever bug volume increases and you need to re-evaluate severity, priority, and assignment. This ensures the backlog remains actionable and regressions are caught before release.