Worktree Isolation

Manage git worktree lifecycle for safe, isolated parallel development.

509 stars

Best use case

Worktree Isolation is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Manage git worktree lifecycle for safe, isolated parallel development.

Teams using Worktree Isolation should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/worktree-isolation/SKILL.md --create-dirs "https://raw.githubusercontent.com/a5c-ai/babysitter/main/library/methodologies/automaker/skills/worktree-isolation/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/worktree-isolation/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How Worktree Isolation Compares

Feature / AgentWorktree IsolationStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Manage git worktree lifecycle for safe, isolated parallel development.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Worktree Isolation

Manage git worktree lifecycle for safe, isolated parallel development.

## Agent
Worktree Manager - `automaker-worktree-manager`

## Workflow
1. Create new branch from base (feature/<id>)
2. Set up git worktree in .worktrees/ directory
3. Verify worktree isolation
4. Install dependencies in worktree
5. After completion, merge or preserve worktree
6. Clean up merged worktrees, preserve failed ones

## Inputs
- `projectName` - Project name
- `featureId` - Feature identifier
- `baseBranch` - Base branch for worktree creation

## Outputs
- Worktree path, branch name, isolation status

## Process Files
- `automaker-orchestrator.js` - Phase 3 (setup) and cleanup
- `automaker-agent-execution.js` - Stage 1
- `automaker-review-ship.js` - Stage 3 (merge)