This skill should be used when the user asks to "/gobby clones", "create clone", "spawn in clone". Manage git clones for isolated parallel development - create, spawn agents, sync, merge, and delete.
Clones create a complete, independent copy of the repository on a separate branch. They're managed via the gobby-clones MCP server. Use progressive discovery for tool schemas.
Default to worktrees. They're lighter, faster, and work with all supported CLIs.
Use clones when you need something worktrees can't provide:
| Need | Use | |------|-----| | Lightweight branch isolation | Worktree | | Quick switching between branches | Worktree | | Disk space matters | Worktree (shared objects) | | Complete isolation from main repo state | Clone | | Independent remote operations (push/pull) | Clone | | Multiple agents that might conflict with each other | Clone | | Risky experiments you want to fully discard | Clone |
Statuses: active → syncing → cleanup (after merge). stale if no recent activity.
1. Create subtasks for parallel work
2. Spawn agents in separate clones (one branch per agent)
3. Each agent works in complete isolation
4. Merge completed clones back to main
5. Handle conflicts with gobby-merge if needed
6. Delete merged clones
Conflicts are detected at merge time, not during development. If a merge fails with conflicts, use gobby-merge tools to resolve them before retrying.
Category:other