Developer tool
repo-manager
A central Git repository registry with output designed for automation.
- Technologies
- Bash · Git · jq · JSON / TSV
- My contribution
- My public CLI for managing multiple repositories.
- Sources checked
Repository ↗ · Documentation ↗
The problem
Working across several repositories requires a quick view of their locations, branches and working tree status. Automation needs the same information in a format that does not require parsing human-oriented terminal output.
Architecture and decisions
The Bash CLI maintains a JSON repository registry. Status is returned as JSON and lists as TSV, while human messages go to stderr. Other scripts can consume the output without stripping decoration or progress messages.
The registry can be populated by scanning existing repositories or cloning new ones. Updates use fetch and pull --ff-only; configuration writes are atomic with flock. Optional git-wt integration exposes worktree management through the same interface.
Status and tradeoffs
Unregistering a repository leaves its files on disk. The README explicitly excludes push, force, reset and repository deletion. Updates can still fast-forward local state; machine-readable output does not replace permission checks or inspecting results.
This is a small infrastructure utility, not an agent scheduler. It contributes repository and worktree visibility to a larger development process.
