triage-bugs

Analyze bug reports to determine severity, priority, and component ownership.

6|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/jerelvelarde/chalk-skills --skill triage-bugs-jerelvelarde
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-bugs
Source: https://github.com/jerelvelarde/chalk-skills/tree/main/skills/triage-bugs
Command: npx skills add https://github.com/jerelvelarde/chalk-skills --skill triage-bugs-jerelvelarde

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage and prioritize bug reports to enable sprint planning and predictable engineering work.

Core Features & Use Cases

  • Read project context: Leverage existing docs and ownership mappings to map bugs to components.
  • Gather bug reports: Ingest bugs from conversation, files, or trackers to compile a unified backlog.
  • Severity, priority, ownership: Apply a matrix to assign severity, estimate impact, and identify owners.
  • Sprint-ready grouping: Group by component and prepare a sprint-ready plan with effort estimates.
  • Report generation: Produce a structured triage report with file-numbering and sprint recommendations.

Quick Start

Provide a list of bugs and a sprint target, and the system outputs a prioritized triage report.

Frequently Asked Questions about triage-bugs

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

FAQPage Schema
How do I triage and prioritize bugs for sprint planning?

Bug triage for sprint planning requires analyzing bug lists to determine reproduction status, severity, priority, and per-component ownership. The system applies a severity matrix, groups issues by component, estimates effort, and outputs a structured sprint-ready report.

What is the best way to assign severity and priority to a backlog of bug reports?

Assigning severity and priority to bug reports uses a defined severity matrix to evaluate impact and reproduction status. This process identifies component ownership and generates a prioritized triage report suitable for engineering documentation.

Can I ingest bug reports from files or issue trackers for triage?

Yes, bug report triage can ingest bugs from conversation context, files, or issue trackers to compile a unified backlog. It leverages existing docs and ownership mappings to map bugs to components for prioritization.

How do I group bugs by component and estimate effort for sprint planning?

Sprint planning groups bugs by component and estimates effort by applying a severity matrix to the unified backlog. This produces a sprint-ready plan with structured file-numbering and effort recommendations.

Does bug triage work without predefined component ownership mappings?

Bug triage leverages existing docs and ownership mappings to accurately map bugs to components. Without these mappings, the system can still assign severity and priority, but component ownership identification may be less precise.