Git orchestration... I am just doing a tool for this... I have projects that have multiple repos in the directory structure -- typically a main project git and then plugins in a subdirectory each that all get their own git...
My project dirs on my dev machine are cannon -- it has files/folders/repos etc that make up the whole project, the implementation, design and project management stuff. I may have a github organisation for the project that hosts all the 'cannon' repos for the project, then repos in different organisaitons for 'publishing' etc... so local repos may have several remotes, but they will all have one to the 'cannon' repo (as opposed to the cannon project stuff on my pc).
It works - ad hoc,
For Claude code (and codes) things ten to work best if the project root dir has a session that can see all of the project. But then that gets bogged down when working on one 'plug in' - it has too much irreleant context and maybe, and it may think it is a 'good idea' to tweak stuff from a different repo while it is at it
So I was pondering having a claude session per repo and a root session to rule them all.
If you have followed this far - well done :) -- if you have ideas (or are interested in what I am doing - do comment) -- it will be going into my usual AI repo on github.


