retrokit
🎮 Retro gaming toolkit — AI-powered platform asset generation and smart ROM collection cleaning 🧰
retrokit is a Python CLI for preparing retro gaming libraries. It generates Pegasus Frontend platform artwork from reference images with Gemini, and it scans ROM folders for duplicate or low-quality variants before you remove them.
Asset generation is built around a local input folder, a Gemini API key, and a theme deployment config. ROM cleaning is local-first: scan, review the CSV report, then quarantine or delete.
Install
git clone https://github.com/tsilva/retrokit.git
cd retrokit
uv tool install .
cp .env.example .env
Set GEMINI_API_KEY in .env before running asset generation commands.
Commands
retrokit assets generate amigacd32 "Commodore Amiga CD32" # generate device and logo assets
retrokit assets list # list generated platforms
retrokit assets themes --init # create themes.yaml
retrokit assets deploy amigacd32 --theme colorful # copy generated assets into a theme
retrokit assets deploy --dry-run # preview deployment
retrokit assets config # show asset configuration
retrokit roms scan --roms-dir /path/to/roms # scan ROMs and write scan_cache.json
retrokit roms report --roms-dir /path/to/roms # write duplicate_report.csv
retrokit roms clean --roms-dir /path/to/roms --dry-run # preview removals from the report
retrokit roms clean --roms-dir /path/to/roms --quarantine # move removals into _quarantine/
retrokit roms clean --roms-dir /path/to/roms --delete # permanently delete after confirmation
For development checks:
uv sync --extra dev
uv run ruff check .
uv run mypy src/retrokit main.py
uv run pytest
Notes
- Asset references live in
.input/<platform_id>/asplatform.jpgorplatform.pngpluslogo.png,logo.jpg, orlogo.jpeg. - Generated assets are written under
output/assets/images/by default: 2160x2160 device PNGs and four 1920x510 logo variants for dark and light themes. - Theme deployment reads
themes.yamlfrom the current directory, the project root, or~/.config/retrokit/themes.yaml. - ROM scans write
scan_cache.json; reports writeduplicate_report.csv; cleaning reads the report rather than rescanning. - ROM cleaning prefers clean dumps, verified tags, higher-priority regions, newer revisions, and preferred per-platform formats. Tune those rules in
src/retrokit/roms.py. main.pyis the original standalone ROM dedup script. The packaged CLI path issrc/retrokit/.
Architecture
License
Metadata
Release files for retrokit 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| retrokit-1.0.1.tar.gz | 2.1 MB | With provenance | Details for retrokit-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| retrokit-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for retrokit-1.0.1-py3-none-any.whl |
Total release size: 2.1 MB
Release files / retrokit-1.0.1.tar.gz
| Download URL | retrokit-1.0.1.tar.gz |
|---|---|
| Size | 2.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
614fae22fa18e26306440b3d2334abbbbf0b4b9587f7860bea77779bbd3586f9
|
|
BLAKE2b-256 checksum How to use checksums |
c707b8bcd707b361adca10810bfdc21f7cad28505575b9d03843b2cabd864ec3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 1, 2026.
Transparency logRelease files / retrokit-1.0.1-py3-none-any.whl
| Download URL | retrokit-1.0.1-py3-none-any.whl |
|---|---|
| Size | 29.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
086060ea8b725b4e06a0a49be8f1007019ac0c21c8ccd270c26141596c996cfd
|
|
BLAKE2b-256 checksum How to use checksums |
895320ad7e280390161aa6dca89b44d2f5887a41bdbd36eda308630506c297be
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 1, 2026.
Transparency logSecurity for retrokit 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for retrokit-1.0.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 1, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.