Gather your skills and AGENTS.md in one repo and point every other repo to it — one session can then work with the whole system in view
The Home Repo Pattern — Matt Pocock (AI Hero) · Read the original ↗
This page is a translation of the Korean original. Read the Korean original →
What you get
- Steering files and tooling sit in one place, so the skill copies duplicated across repos disappear
- One session can plan and carry out changes that span several repos
- If the team shares the repo, everyone runs agents on the same skills and rules
When to use it
Use it when a project spans several repos, so an agent started in one repo sees only that repo, and as an alternative when a monorepo is not an option (a mix of public and private repos, or a team that will not accept a monorepo). Also use it when a team shares the repo and everyone runs agents inside it.
How to do it
- Open a new coding-agent session in the folder that holds your repos and paste in the setup prompt.
- Step 1: find every git repo under your home directory and record its path, remote, public/private status and last commit date; then answer which repos to point to, where the Home Repo goes, whether it is personal or team-shared, and which files load at session start.
- Step 2: list every skill, AGENTS.md, CLAUDE.md and agent-facing doc in the chosen repos and the user-level skills folder, and sort each into one of four buckets: shared, duplicate, repo-specific or installed.
- Step 3: review and approve a table showing each item's current location and destination, plus a draft AGENTS.md for the Home Repo (an 'Other Repos' section with one pointer line per repo).
- Step 4: create the Home Repo and its AGENTS.md and copy shared items over as whole skill folders; then, in each child repo, create a new local branch, remove the copies that moved, and commit to the Home Repo (you decide when to push).
Try it now
Open an agent session in the folder that holds your repos and paste in the setup prompt from the post. The agent surveys your repos and skills on its own and returns a table sorting them into shared, duplicate, repo-specific and installed — which shows how many duplicate skills and instruction files have actually piled up in your setup. Until you approve, it only reads, so you can run it as a health check without worrying that files will change.
Links
- OriginalThe Home Repo Pattern
- OtherHome Repo
- Otherskills
- OtherAGENTS.md
- Otherprogressive disclosure
- Othersoftware factory
Background — what the original covers
Run an agent on a project split across several repos and it sees only the repo it started in, while skills and settings pile up as separate copies in each repo. As an alternative, Matt Pocock proposes keeping one repo that holds the shared skills and instruction files and starting every session from it. The setup is meant for cases where a monorepo is not possible, especially environments that mix public and private repos.