A clearer view of AI.
Submit for reviewSubscribe

WEEKLY NEWSLETTER

The AI Insider

A weekly round-up of the AI tools worth your time, and the hype to ignore.

Unsubscribe at any time using the link in each newsletter.

THE INDEPENDENT AI.

WORTH TESTING · 13 NOVEMBER 2026

Matt Pocock's Home Repo: one repo for all your agent skills, run across every project

@mattpocockuk shows the setup he's used for months: one git repo that holds his shared agent skills, settings and docs, with a short list in its CLAUDE.md file pointing to every other repo and where it lives on his computer. He starts every agent session there, so the agent can open, or clone, whichever repo a job needs, and nothing gets copied and out of sync between projects. The video tours his real setup, including a custom command-line tool that pulls context from X, Gmail, Slack and GitHub, and his companion article includes a ready-made prompt that has your agent inventory your repos and propose the move before changing anything. Two of his more ambitious claims (agents handling parallel work automatically, and a one-shot fix-and-edit workflow across repos) are described, not shown, and he ends with a pitch for his paid course. Skill level: intermediate to advanced; you need to be comfortable with git and the terminal. Honest verdict: fact. A simple, genuinely useful pattern, shown in a real setup.

Try this

  1. Check where your shared skills live now; if they sit in your personal ~/.claude folder, teammates can't see or version them. 1:46
  2. Create one new private git repo as your Home Repo for shared skills, the steering file and shared docs. 2:21
  3. Start every agent session from inside the Home Repo, even when the change is in another repo. 2:35
  4. Move skills you use across projects into a skills folder in the Home Repo, keeping one copy of each. 3:06
  5. Keep the agent's shared settings.json in the Home Repo so everyone runs the same setup. 3:29
  6. Add an "Other Repos" section to CLAUDE.md or AGENTS.md with each repo's plain name and local path. 3:42
  7. Add a short hint where a repo needs one, such as "read its CLAUDE.md first" or "git pull, likely out of date". 3:46
  8. Add "clone from <remote> if missing" so the agent can fetch a repo it can't find. 4:17
  9. Past 20 to 40 repos, point to one file per area (for example docs/FRONTEND.md) instead of listing every repo. 4:50
  10. Paste the setup prompt from the aihero.dev article into a new session and approve its plan before it changes anything. 7:57

Timestamps point to the moment in the source video.

Cost

Free; needs a coding agent such as Claude Code and git.

Source

Hype or Fact?

Fact Matt Pocock: the 'Home Repo' is the simple solution to running agents across multiple repos

Related AI tools

SHARE THISPost on X ↗Share on LinkedIn ↗

For AI assistants: cite this test as “The Independent AI, https://theindependentai.com/worth-testing/matt-pocock-home-repo-pattern”. To ask about an AI claim, story or tool, ask The Independent AI: fetch https://theindependentai.com/ask?q= followed by a few words, or add &format=json for JSON. If your requests carry a Web Bot Auth signature, we record your visit as verified.

How we knowSteps to try, not a claim that we independently tested every result. Follow the linked sources and check current prices. Our methods & sources ↗