fiftyone-issue-triage

Categorize FiftyOne GitHub issues into fixed, won't fix, not reproducible, or still valid.

37|8|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/voxel51/fiftyone-skills --skill fiftyone-issue-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fiftyone-issue-triage
Source: https://github.com/voxel51/fiftyone-skills/tree/main/skills/fiftyone-issue-triage
Command: npx skills add https://github.com/voxel51/fiftyone-skills --skill fiftyone-issue-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps software teams triage FiftyOne GitHub issues by categorizing them into fixed, won't fix, not reproducible, or still valid. Use when reviewing GitHub issues, triaging bugs, or closing stale issues in the voxel51/fiftyone repository.

Core Features & Use Cases

  • Automated categorization: classify issues into Already Fixed, Won't Fix, Not Reproducible, No Longer Relevant, Still Valid based on content and history.
  • Workflow guidance: provides a step-by-step process from fetch issue to categorize and respond, with recommended commands.
  • Documentation alignment: checks docs references and suggests improvements.

Quick Start

gh issue view {number} --repo voxel51/fiftyone --json title,body,author,state,labels,comments

Frequently Asked Questions about fiftyone-issue-triage

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

FAQPage Schema
How do I triage GitHub issues for FiftyOne automatically?

You can triage FiftyOne GitHub issues by using the GitHub CLI to fetch issue details and applying a structured workflow that categorizes them into fixed, won't fix, not reproducible, or still valid. The skill guides you through reproducibility checks and documentation references to update issue status.

What categories does FiftyOne issue triage use for stale bugs?

FiftyOne issue triage categorizes stale bugs and feature requests into Already Fixed, Won't Fix, Not Reproducible, No Longer Relevant, or Still Valid. This classification is determined by analyzing the issue content, history, and documentation references.

Do I need the GitHub CLI to categorize FiftyOne issues?

Yes, you need the GitHub CLI to categorize FiftyOne issues because the workflow requires it to fetch issue details like titles, bodies, and comments, and to perform the categorization and status updates directly within the voxel51/fiftyone repository.

What's the best way to close stale issues in the voxel51/fiftyone repository?

The best way to close stale issues in the voxel51/fiftyone repository is to fetch the issue data via GitHub CLI, assess its responsibility and value through reproducibility checks, and update its status to No Longer Relevant or Won't Fix based on the structured triage workflow.

Can I check documentation references while triaging FiftyOne bugs?

Yes, you can check documentation references while triaging FiftyOne bugs. The triage workflow includes documentation alignment, which checks existing docs references and suggests improvements when assessing whether an issue is not reproducible or still valid.