bmad-os-gh-triage

To prioritize open GitHub issues, you can analyze issue metadata, labels, and bodies to classify priority and generate a structured triage report. This separates critical blockers from low priority work without relying on time estimates.

Yes, you can group duplicate GitHub issues and map related themes by analyzing issue titles and bodies. This process spots duplicates, clusters related items, and identifies cross-repository routing decisions for misplaced bugs.

Yes, you need gh CLI access to analyze repository bugs and generate a triage report. The analysis requires gh CLI to fetch issue metadata needed to classify priority and produce actionable markdown output.

The best way to turn scattered GitHub feature requests into an action plan is to batch-analyze the backlog to determine real problems and impact. This generates a markdown summary with executive insights and actionable next steps.

Issue triage handles cross-repo routing decisions by reviewing issue metadata to identify items that belong elsewhere. It maps relationships across repositories to ensure unresolved bugs are routed correctly.

A limitation when classifying priority for open GitHub issues is that classification relies entirely on available issue metadata like titles, bodies, and labels. Issues lacking detailed metadata may result in less accurate priority assignments.