SpecBridge Overview
Every spec in SpecBridge has a full version history, similar to how Git tracks code changes. You can see what changed between versions, who changed it, and restore any previous version at any time.
Why Version Specs?
- Track changes — see exactly what was added, removed, or modified between versions
- Collaborate safely — multiple people can work on specs without stepping on each other
- Go back in time — revert to an earlier version if something goes wrong
- Stay in sync — push and pull changes to keep everyone on the same page
How It Works
From the CLI, you work with specs just like you would with code:
specbridge add— stage your spec files for the next commitspecbridge commit— create a local snapshot with a message describing what changedspecbridge push— upload your commits to the server so your team can see themspecbridge pull— download the latest changes from your teammates
flowchart TB
WT["Working Tree
(spec files)"] -->|"specbridge add"| STAGE["Staging Area"] STAGE -->|"specbridge commit"| COMMIT["Local Commit"] COMMIT -->|"specbridge push"| SERVER["Server
(team-visible)"] SERVER -->|"specbridge pull"| COMMIT
(spec files)"] -->|"specbridge add"| STAGE["Staging Area"] STAGE -->|"specbridge commit"| COMMIT["Local Commit"] COMMIT -->|"specbridge push"| SERVER["Server
(team-visible)"] SERVER -->|"specbridge pull"| COMMIT
Conflict Handling
If two people edit the same spec at the same time, SpecBridge flags the conflict so you can resolve it before pushing — no silent overwrites.
History and Diff
specbridge log— browse the full commit history for any specspecbridge diff— see exactly what changed between two versionsspecbridge checkout— switch to any previous versionspecbridge revert— undo a specific commit
Version Numbers
Every time a spec is pushed to the server, its version number increments automatically. The dashboard shows which version is current and lets you browse the full history.