Skip to main content

Repositories and Commits

There are following repositories:

  • Repositories/ — Contains the actual source code of the application, organized by module (e.g., frontend and backend repos).
  • Swifter/ — Swifter orchestration layer containing work item definitions, project structure, module specifications (design system, framework patterns, boilerplate conventions), and work item artifacts.

After Swifter (via its agents — developer, analyst, etc.) makes changes to a module, commits are created in the respective module's repository. So:

  • Changes to frontend code → committed to Repositories/your_project_name.frontend
  • Changes to backend code → committed to Repositories/your_project_name.backend
  • Changes to specs/artifacts → committed to Swifter/

Each repo gets its own commits independently. No complex cross-module branch syncing — just commits going to whichever repo was modified.

Commits act as a changelog of Swifter's work — you can review the git history of each repo to see what was changed, when, and by which step of the workflow. Makes it easy to track progress, review individual changes, or roll back if needed.

The Swifter UI has a Dev tab that embeds a VS Code-like Source Control panel. Each repo shows its own changes and commits. At the bottom there's a Git Graph view where you can visually follow the commit history.