RepoPilot

debpalash / voicestudio

Search debpalash/voicestudio

GitHub

Code

How debpalash/voicestudio is laid out, and where to start for common changes.

There is no import map for this report yet.

Where to start reading

  1. Repository root
  2. Repository root
  3. Likely public API
  4. Likely public API
  5. Likely start-up file
  6. Likely start-up file
  7. Suggested starting pointAI
  8. Suggested starting pointAI

Find files for a task

AI

Add a New Voice Engine (TTS/ASR variant)

  • Create new engine module under backend/engines/ (e.g., backend/engines/_my_engine/)
  • Register engine in backend/config/models.yaml with metadata and model paths
  • Update backend/api/public_engine_metadata.py to expose new engine in /engines endpoint
  • Add engine selection logic to backend/services/__init__.py to route requests appropriately

Add a New API Endpoint

  • Define request/response schema in backend/schemas/requests.py
  • Create route handler in backend/api/__init__.py or new file in backend/api/
  • Inject required services via backend/api/dependencies.py dependency system
  • Add corresponding Electron client method in electron/src/main/account/account-api.ts

Add a New Workflow (e.g., audiobook creation variant)

  • Create CLI command in omnivoice/cli/ (e.g., omnivoice/cli/audiobook.py) matching omnivoice/cli/dub.py pattern
  • Implement workflow logic as a Service in backend/services/__init__.py or new dedicated file
  • Add data processing logic to omnivoice/data/ (batching, collation, validation)
  • Wire workflow into backend/api/__init__.py as a new endpoint

Support a New Language or Voice Model

  • Add model definition to backend/config/models.yaml with language code and metadata
  • Register model licensing in backend/config/model_licenses.json if required
  • Update language/model dropdown data in config/distributions.d.mts for UI exposure

Change the public API

Trace runtime behavior

Add or update tests

Change build or automation

RepoPilot lists up to 500 files, so a file missing here may still exist.

  • Files marked “likely” are guessed from their names.

Code quality and hotspots

Largest source files

  • Branch points115 per file on average
  • Code issues1 error, 37 warnings
  • Largest file4,237 lines
  • Hotspot load10 high-risk files

Static checks on the 15 largest source files.

Tests, CI and tooling

  • CIGitHub Actions18 workflows
  • Tests1,655 test filesPytest · 1.2 test files per source file (file count, not coverage)
  • Dependency updatesNo config detected

Test folders: backend/tests

Hotspots

Files that change often and branch heavily, highest first. Branch points count if, loop, case, catch, ternary, && and || in the file.