| name | setup-multi-repo |
| description | Set up a multi-clone repo folder structure with 5 slot clones for parallel Claude Code agent work. Use when the user says "set up multi-repo", "setup slots", "create repo slots", or wants to create the same folder pattern used for towles-tool-repos. |
| user_invocable | true |
Setup Multi-Repo Folder Structure
Create a parent directory containing 5 -slot-N clones of the same GitHub repo. This pattern
supports running multiple Claude Code agents in parallel, each in its own isolated working copy.
Structure
~/code/p/<name>-repos/
<name>-slot-1/ # Slot 1
<name>-slot-2/ # Slot 2
<name>-slot-3/ # Slot 3
<name>-slot-4/ # Slot 4
<name>-slot-5/ # Slot 5
Steps
-
Ask the user for:
- The GitHub repo URL (e.g.,
https://github.com/ChrisTowles/blog.git)
- The short name to use for the folder/clones (e.g.,
blog)
- The parent directory (default:
~/code/p/)
-
Create the parent directory:
mkdir -p ~/code/p/<name>-repos
-
Clone 5 slots:
cd ~/code/p/<name>-repos
for i in 1 2 3 4 5; do
git clone <repo-url> "<name>-slot-$i"
done
-
Verify the structure:
ls -la ~/code/p/<name>-repos/
Example
For the blog repo:
mkdir -p ~/code/p/blog-repos
cd ~/code/p/blog-repos
for i in 1 2 3 4 5; do
git clone https://github.com/ChrisTowles/blog.git "blog-slot-$i"
done
Notes
- Each slot is a fully independent git clone (not a worktree) so agents can freely switch branches
- Slots are interchangeable — use any idle slot for manual work or hand it to an agent
- Slot clones are managed by the agentboard system in towles-tool
- If the repo already has a standalone clone (e.g.,
~/code/p/blog), consider removing it after migration