# Apply FiftyOne Python Code Style

FiftyOne contributors need consistent Python style across imports, docstrings, utilities, and validation. This skill provides focused conventions and checklists for compatible code.

## Install

```bash
npx skillstore add adonaivera/fiftyone-code-style
```

## Metadata

- Status: approved
- Slug: adonaivera-fiftyone-code-style
- Skillstore revision: r1
- Version status: missing
- Tree hash: d50a7c437d3c0cd8bfdd7c00bcf241031e6dc476ebfa6c7a542b6f35ba3896c2
- Author: AdonaiVera
- GitHub username: AdonaiVera
- License: MIT
- Repository: https://github.com/AdonaiVera/fiftyone-skills/tree/main/code-style/skills/fiftyone-code-style
- Ref: c1fdca50ff516318f65fed0d7f9e82797c5171dc
- 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, network
- Quality score: 79
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/adonaivera-fiftyone-code-style
- Manifest: https://skillstore.pages.dev/api/skills/adonaivera-fiftyone-code-style/manifest

## Capabilities

- Provides a module template with header docstring, imports, logger setup, public functions, and private helpers.
- Defines FiftyOne import groups and common aliases for core modules and utilities.
- Shows Google-style docstring patterns for functions, classes, arguments, returns, and raised errors.
- Recommends lazy imports, optional dependency guards, and non-fatal warning patterns.
- Includes a checklist for style compliance, quality checks, linting, formatting, and tests.
- Directs users to reuse FiftyOne and eta utilities before adding redundant implementations.

## Use Cases

- Prepare FiftyOne Contributions: Align new modules, imports, docstrings, and helper functions with FiftyOne repository conventions before submitting a pull request.
- Build Consistent Plugins: Use the documented aliases, lazy import guidance, and validation checklist when writing FiftyOne plugin code.
- Review Python Changes: Compare proposed code against a compact checklist for import ordering, utility reuse, docstrings, logging, and tests.

## Prompt Templates

### Format A Module

```
Review this Python module for FiftyOne code style. Focus on import groups, aliases, module layout, logger setup, and private helper naming.
```

### Improve Docstrings

```
Rewrite these docstrings in the FiftyOne Google-style pattern. Include Args, Returns, and Raises sections only where they apply.
```

### Check Utility Reuse

```
Inspect this implementation for redundant helpers. Suggest existing FiftyOne or eta utilities that may replace custom path, JSON, image, or type-checking logic.
```

### Review A Pull Request

```
Perform a FiftyOne style pass on this change. Check import organization, lazy imports, guard patterns, warning behavior, utility reuse, tests, and lint commands.
```

## Limitations

- It is guidance only and does not run formatting, linting, or tests by itself.
- It focuses on FiftyOne Python conventions, not general style for every Python project.
- It does not replace project maintainers, CI rules, or code review requirements.
- It does not validate whether referenced FiftyOne APIs are available in every installed version.

## Best Practices

- Use the import group order before making deeper style changes.
- Check existing FiftyOne and eta utilities before creating new helper functions.
- Run linting, formatting checks, and targeted tests after applying the guidance.

## Anti Patterns

- Do not treat the examples as a complete replacement for repository CI.
- Do not add heavy imports at module load time when lazy imports are appropriate.
- Do not create duplicate utilities without checking FiftyOne and eta modules first.

## Security Audit

- Audited at: 2026-07-06T01:44:00.856\+00:00
- Summary: All 74 static findings were adjudicated as false positives. The matches are Markdown code fences, inline code, a documentation URL, fixed example validation commands, or a style-guide heading, with no executable malicious behavior found.

## Stats

- Views: 292
- Downloads: 10
- Favorites: 0
- Popularity score: 0