# Triage FiftyOne Issues

Maintainers often need consistent issue triage across reports, comments, and code evidence. This skill provides a focused workflow and response templates for FiftyOne GitHub issues.

## Install

```bash
npx skillstore add adonaivera/fiftyone-pr-triage
```

## Metadata

- Status: approved
- Slug: adonaivera-fiftyone-pr-triage
- Skillstore revision: r1
- Version status: missing
- Tree hash: 5748ff1a1354b45d80f808b82a7bb77a2596e5a784912e4e988beb2eb2e90d0c
- Author: AdonaiVera
- GitHub username: AdonaiVera
- License: MIT
- Repository: https://github.com/AdonaiVera/fiftyone-skills/tree/main/pr-triage/skills/fiftyone-pr-triage
- Ref: 6eec4a59f63ff83440a84c18d1aef79743bc714e
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/adonaivera-fiftyone-pr-triage
- Manifest: https://skillstore.pages.dev/api/skills/adonaivera-fiftyone-pr-triage/manifest

## Capabilities

- Classifies GitHub issues into five triage outcomes.
- Guides reviewers through issue details, code search, git history, and related issue checks.
- Provides response templates for fixed, invalid, stale, unreproducible, and still valid issues.
- Includes a checklist for reproduction, root cause review, and category selection.
- Shows standard code reference formatting for maintainer replies.

## Use Cases

- Reduce Maintainer Backlog: Apply consistent categories and response templates when processing older FiftyOne issues.
- Validate Bug Reports: Check code references, recent commits, and reproduction evidence before deciding whether a bug is still valid.
- Draft Support Responses: Create clear issue replies that explain the decision, evidence, and next action for the reporter.

## Prompt Templates

### Classify One Issue

```
Read this FiftyOne issue summary and classify it using the five triage categories. Explain the evidence and draft a short response.
```

### Check For Prior Fixes

```
Use the workflow to compare this issue with recent commits and closed issues. Decide if it is already fixed or still valid.
```

### Prepare Maintainer Reply

```
Based on this investigation summary, choose the best category and write a maintainer reply with evidence, next steps, and respectful tone.
```

### Audit A Backlog Batch

```
Triage these related FiftyOne issues as a batch. Group duplicates, identify stale reports, flag still valid bugs, and propose closure comments.
```

## Limitations

- The workflow is focused on the FiftyOne project and its issue categories.
- It does not connect to GitHub or run commands by itself.
- Reviewers must still verify reproduction results and project scope decisions.
- Command examples require a local repository and optional GitHub CLI access.

## Best Practices

- Verify issue details, comments, and reported FiftyOne version before assigning a category.
- Use repository evidence, linked pull requests, and reproduction results to support each response.
- Keep replies concise, respectful, and clear about next steps for the reporter.

## Anti Patterns

- Close an issue only because it is old.
- Claim a fix without evidence from commits, releases, or related issues.
- Run command examples against untrusted repositories without reviewing the command and environment.

## Security Audit

- Audited at: 2026-07-05T01:42:55.425\+00:00
- Summary: Static alerts are caused by Markdown fences, inline code formatting, and documented local investigation commands. I found no prompt injection, data exfiltration, credential access, obfuscated code, or unauthorized execution intent in SKILL.md.

## Stats

- Views: 233
- Downloads: 9
- Favorites: 0
- Popularity score: 0