bug-triage

Name: bug-triage
Availability: InStock
Author: carlosq96

Classify bugs by severity and priority into a sprint-ready triage report.

Updated Apr 9, 2026

Search Tags:#backlog #priority #report #severity #sprint-planning #bug-triage

Ready to run

npx skills add https://github.com/CarlosQ96/robot-crawler --skill bug-triage-carlosq96

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bug-triage
Source: https://github.com/CarlosQ96/robot-crawler/tree/main/.agents/skills/bug-triage
Command: npx skills add https://github.com/CarlosQ96/robot-crawler --skill bug-triage-carlosq96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates bug backlog triage to convert open issues into a prioritized, sprint-ready action list, ensuring critical issues are surfaced and reducing manual triage effort.

Core Features & Use Cases

Classify every bug by severity and priority to drive sprint planning.
Load backlog from production/qa/bugs and understand current sprint context to assign to sprint or backlog.
Generate a formal triage report highlighting open P1/P2 bugs, systemic trends, and risk.
Provide trend analysis data such as volume, hot spots, and aged bugs to guide engineering focus.
Support modes: sprint (current sprint allocation), full (complete backlog triage), and trend (read-only analysis).

Quick Start

Run /bug-triage sprint to begin triaging the current open bugs for the active sprint.

Frequently Asked Questions about bug-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate bug triage for sprint planning?▼

Automate bug triage by classifying open issues by severity and priority to generate a sprint-ready action list. It assigns bugs to the current sprint or backlog based on loaded context, reducing manual triage effort.

What is the best way to prioritize a bug backlog by severity?▼

Prioritize a bug backlog through deterministic classification by severity and priority. This process surfaces open P1 and P2 bugs in a formal triage report, ensuring critical issues are addressed first during sprint planning.

How do I generate a bug triage report with trend analysis?▼

Generate a bug triage report with trend analysis by running a full backlog review or read-only trend mode. This analyzes volume, hot spots, and aged bugs to guide engineering focus and highlight systemic risks.

Can I load production QA bugs into sprint-bound triage?▼

Yes, you can load open issues from production QA bug tracking workflows into sprint-bound triage. The process reads current sprint context to assign bugs appropriately to either the active sprint or the backlog.

Does bug triage work for full backlog reviews or only current sprints?▼

Bug triage works for both full backlog reviews and current sprints. It supports three modes: sprint for current allocation, full for complete backlog triage, and trend for read-only analysis of volume and hot spots.

Why are aged bugs not being surfaced in my triage report?▼

Aged bugs may not surface if you are using sprint mode instead of trend or full mode. To surface aged bugs and volume hot spots, run a read-only trend analysis or a complete backlog triage to guide engineering focus.