clones

Manage isolated git clones with MCP commands for parallel development.

19|3|Updated Dec 15, 2025
One-click install
npx skills add https://github.com/GobbyAI/gobby --skill clones
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clones
Source: https://github.com/GobbyAI/gobby/tree/main/src/gobby/install/shared/skills/clones
Command: npx skills add https://github.com/GobbyAI/gobby --skill clones

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill centralizes and automates the management of git clones to enable isolated parallel development, ensuring agents can run without impacting the main repository.

Core Features & Use Cases

  • Create, spawn, sync, merge, and delete isolated clones to run agents in parallel.
  • Manage clone lifecycles and session context integration for reliable, auditable workflows.
  • Use cases include parallel feature development, experimentation, and safe handoff of work back to main.

Quick Start

Use the skill to create a new clone for a feature branch, then spawn an agent in that clone and later merge or delete as needed.

Frequently Asked Questions about clones

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run parallel development on a git repository without interfering with the main branch?

Isolated git clones enable parallel agent development without impacting the main repository. You create a clone, spawn an agent inside it, and later sync or merge the isolated changes back to the main workstream.

How do I manage the lifecycle of isolated git clones for feature branches?

Managing isolated git clone lifecycles involves using MCP-based commands to create, spawn, sync, merge, and delete clones. This handles session context integration to ensure reliable and auditable parallel feature workflows.

Can I spawn AI agents directly inside a git clone for parallel feature development?

Yes, you can spawn agents directly inside isolated git clones for parallel feature development. The clone provides a safe, isolated environment for the agent to make changes before you sync and merge them.

What is the best way to sync and merge changes from parallel workstreams back to a main repository?

The best way to sync and merge parallel workstreams is using MCP-based sync and merge commands on isolated clones. This safely consolidates changes from multiple agents back into the main repository without conflicts.

Do I need MCP to manage isolated clones for parallel agents?

Yes, this approach uses MCP-based commands to manage isolated clones for parallel agents. The MCP protocol provides the specific create, spawn, sync, merge, and delete commands needed for clone lifecycle and session context integration.