fiftyone-issue-triage

Included with Lifetime

$97 forever

Triages FiftyOne GitHub issues by categorizing as 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.

Code Review

What this skill does


# FiftyOne Issue Triage

## Categories

| Category | When to Use |
|----------|-------------|
| **Already Fixed** | Resolved in recent commits/releases |
| **Won't Fix** | By design, out of scope, or external behavior (browser, OS, third-party) |
| **Not Reproducible** | Cannot reproduce with provided info |
| **No Longer Relevant** | Outdated version, deprecated feature, or stale (6+ months) |
| **Still Valid** | Confirmed bug or valid feature request needing work |

## Workflow

### 1. Fetch Issue
```bash
gh issue view {number} --repo voxel51/fiftyone --json title,body,author,state,labels,comments
```

### 2. Analyze
- Extract: issue type, version, reproduction steps, error message
- Search related: `gh issue list --repo voxel51/fiftyone --state all --search "keyword"`
- Check git history: `git log --oneline --grep="keyword"`

### 3. Assess Responsibility
- External behavior (browser, OS, third-party)? → Won't Fix
- User workflow/configuration issue? → Won't Fix (with workaround)
- FiftyOne code/behavior issue? → Continue assessment

### 4. Assess Value
Before proposing fixes, ask: "Is a fix worth the effort?"
- How many users affected?
- Is workaround simple?
- Would fix add complexity or hurt performance?

### 5. Check Documentation
```bash
grep -r "keyword" docs/source/ --include="*.rst"
```

### 6. Categorize and Respond

## Quick Reference

| Category | Key Indicator | Action |
|----------|---------------|--------|
| Already Fixed | Found in git log | Point to PR, suggest upgrade |
| Won't Fix | External/by design | Explain, provide workaround |
| Not Reproducible | Can't reproduce | Request more info |
| No Longer Relevant | Old/stale/deprecated | Explain, suggest new issue |
| Still Valid | Confirmed, no fix | Document root cause, propose fix |

## Response Tone

Always start with thanks, be friendly, then explain. Keep responses simple (no internal code details).

## If User Willing to Contribute

- **Contribution guide:** https://docs.voxel51.com/contribute/index.html
- **Discord:** https://discord.com/invite/fiftyone-community (#github-contribution channel)
- Point to relevant code files for the fix

Files: 2

Size: 3.6 KB

Complexity: 9/100

Category: Code Review

Source: https://github.com/voxel51/fiftyone-skills/tree/main/skills/fiftyone-issue-triage

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts