I work across a handful of sibling repos (frontend, backend, shared libs). Claude Code is great inside one repo but kept tripping over the workspace: pulling repos one at a time, building them in the wrong order, and not noticing that a change to a shared lib broke the app right next to it. So I built ezgitx, a small Rust CLI with output meant for agents instead of humans. It does four things: status across every repo at once pull everything, fast-forward only build or test across all repos in dependency order (run --all --with-deps) check-impact: change a shared lib, get back everything downstream that needs re-checking It writes a skill file into the workspace, so a fresh Claude Code session finds it and uses it on its own. You don’t need to explain the tool to the agent. What it does not do: understand your code semantically. It’s the operational layer (what’s stale, what order, what’s affected), not a code-comprehension tool. Pair it with your context docs. Repo, install, and a paste-one-prompt setup: github.com/yuval- r/ezgitx . Would love feedback on the agent output contract, that’s the part I went back and forth on most. submitted by /u/yuval888
Originally posted by u/yuval888 on r/ClaudeCode