The home repo pattern

Do you have an AI workflow that involves creating files that you don't want to be added to the repo you are working on? For example, you might be working in a team where there isn't a generally agreed-upon approach to AI-augmented development, and for political reasons you don't want to force your approach on your teammates. This can be solved by using the home repo pattern.

The pattern

I first came across this pattern in a video by Matt Pocock (who coined its name):

Essentially, it is just a sibling repo - the home repo - that acts as a container for your AI workflow files. From this repo your AI agent hops across into other repos as it needs.

I have been actively thinking about how to solve this problem, so when this video popped up it was very timely.

An alternative pattern

The other approach I have been considering (before I saw Matt Pocock's) - which is really just a variation on this - is the meta-repo pattern. You can see a good video on it here by Matt Walters:

I haven't fully decided on which approach is best - when I do, I will probably write a post about it.