bug-triage

Classify markdown bug reports into prioritized sprint-aware triage reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts an unprioritised backlog of markdown bug reports into a clear, actionable triage output so teams can ensure critical defects are found, prioritized, and assigned before a sprint starts or QA hand-off.

Core Features & Use Cases

  • Severity and Priority Classification: Extracts or infers S1–S4 severity and P1–P4 priority for each bug.
  • Sprint-aware Assignment: Matches P1/P2 items to the current sprint where capacity allows and flags overflow for owner decisions.
  • Trend Analysis & Systemic Detection: Computes volume, hotspots, age, and regression indicators and surfaces systemic issues requiring engineering review.
  • Report Generation with Guardrails: Produces a human-readable triage report (production/qa/bug-triage-[date].md) and asks for explicit user approval before writing.

Quick Start

Run bug-triage in sprint mode to classify open bugs, detect trends, and prepare a triage report for the current 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 and assign open bugs for sprint planning?

To prioritize and assign open bugs for sprint planning, you process markdown bug reports to infer S1–S4 severity and P1–P4 priority, matching high-priority fixes to current sprint capacity while flagging overflow for owner decisions.

What is bug triage and how does severity classification work?

Bug triage is the process of converting an unprioritized backlog into an actionable report. Severity classification works by evaluating markdown bug reports to infer S1–S4 severity and P1–P4 priority designations for QA hand-off decisions.

Can I detect systemic issues and compute trend metrics from a bug backlog?

Yes, you can detect systemic issues and compute trend metrics from a bug backlog by analyzing volume, hotspots, age, and regression indicators, surfacing issues that require engineering review for your QA planning decisions.

Does the bug triage report generation require user approval before writing?

Yes, bug triage report generation requires explicit user approval before writing. The process computes trend metrics and prepares a human-readable triage report file, only writing to production after receiving final user confirmation.

What's the best way to handle sprint capacity overflow when assigning bug fixes?

The best way to handle sprint capacity overflow when assigning bug fixes is to match P1 and P2 items to the current sprint where capacity allows, explicitly flagging remaining overflow items for owner decisions.

When do I need to generate a markdown triage report for QA hand-off?

You need to generate a markdown triage report for QA hand-off when you have an unprioritized backlog of open bugs and must ensure critical defects are found, prioritized, and assigned before a sprint starts.