bug-triage

Apply priority and area labels to GitHub issues labeled requires-triage.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/sp-202/datafusion-comet-geo --skill bug-triage-sp-202
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-triage
Source: https://github.com/sp-202/datafusion-comet-geo/tree/main/.claude/skills/bug-triage
Command: npx skills add https://github.com/sp-202/datafusion-comet-geo --skill bug-triage-sp-202

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually triaging many GitHub issues labeled for review wastes maintainer time and delays correct prioritization and routing.

Core Features & Use Cases

  • Priority + area labeling using the canonical triage guide: Applies the project’s decision tree to every open issue tagged requires-triage.
  • Safe state transitions with traceability: Removes requires-triage only when labels are successfully applied, and records rationale in a dated summary issue.
  • Human-in-the-loop verification: A reviewer validates the summary issue and closes it when satisfied.

Quick Start

Ask the AI to run the bug-triage skill to triage all open requires-triage issues in the Apache DataFusion Comet repository and produce a dated summary issue for human review.

Frequently Asked Questions about bug-triage

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

FAQPage Schema
How do I automate GitHub issue triage for my repository?

Automating GitHub issue triage involves applying priority and area labels to open issues marked `requires-triage` using a canonical decision tree. This removes the manual burden of classifying bugs and ensures consistent prioritization for maintainers.

What is the best way to prioritize bugs in Apache DataFusion Comet?

Bug prioritization in Apache DataFusion Comet is handled by applying correct priority and area labels to issues using a canonical triage guide. The process automatically classifies open issues and generates a dated summary issue for human spot-checking.

Does automated issue triage work with existing GitHub labels?

Yes, automated issue triage works with existing GitHub labels by applying the project's correct priority and area labels strictly without creating new ones. It safely transitions state by removing `requires-triage` only after labels are successfully applied.

How do I maintain human-in-the-loop verification when automating bug prioritization?

To maintain human-in-the-loop verification during bug prioritization, the automated process files a dated summary issue containing the applied labels and rationale. A human reviewer then validates this summary issue and closes it when satisfied.

What are the limitations of using GitHub CLI for issue label management?

A limitation of using GitHub CLI for issue label management is that it requires strict guardrails to avoid creating unauthorized labels. The triage process must only apply existing priority and area labels and safely remove `requires-triage` upon successful classification.