Run parallel agents in isolated git worktrees with overlap validation.
npx skills add https://github.com/quickcall-dev/skills --skill worktree-fleet
Please help me install this Agent Skill. Skill: worktree-fleet Source: https://github.com/quickcall-dev/skills/tree/main/skills/worktree-fleet Command: npx skills add https://github.com/quickcall-dev/skills --skill worktree-fleet
worktree-fleet prevents parallel agent edits from colliding by isolating each worker in its own git worktree and branch, then validating that workers do not overlap on the files they claim to touch.
Use when: refactoring multiple modules at once, updating separate docs, or making concurrent changes across non-overlapping parts of a repo where you still want git history and clean separation.
Launch a merge-safe parallel fleet by creating a fleet.json with distinct target_files per worker, writing a prompt.md for each worker, then running bash ${AGENTS_SKILLS_DIR}/scripts/launch.sh /absolute/path/to/fleet-root.
High-intent search queries and answers about installing and using this skill.
Git worktree isolation for parallel agents works by spawning each worker in a separate branch and worktree, then validating non-overlapping target files. This prevents irreversible merge conflicts by ensuring workers only edit distinct file globs before they are launched.
Orchestrating multiple AI agents on separate files requires declaring distinct target_files per worker in a fleet.json configuration. The system validates file glob overlaps before launch, spawning each agent in an isolated git worktree and branch for safe parallel execution.
Yes, tmux is required to spawn parallel workers in isolated git worktrees. The orchestration process uses tmux-based worker spawning alongside dependencies including jq, git, python3, stat, and pgrep to manage independent agent sessions.
You validate branch isolation by running a mandatory dry-run validation that detects file glob overlaps across workers' declared target_files. The system refuses to launch when any two workers' globs overlap, ensuring safe orchestration before spawning.
Yes, parallel git worktrees support concurrent documentation updates and refactoring tasks. This approach applies to one-shot parallel tasks where workers edit non-overlapping file globs, capturing changes as separate commits in isolated branches for clean git history.
Parallel agent orchestration refuses to launch when workers' declared target_files overlap to prevent irreversible merge conflicts. The system detects glob pattern overlaps during pre-launch independence validation, enforcing strict file isolation for safe orchestration.
INNERJOINTManage isolated git worktrees and tmux sessions for issues and pull requests.
swissonidValidate tests and guide merge, PR, or cleanup workflows for git branches.
AcurioustractorOrchestrate parallel AI agents across ACT projects with isolated git worktrees.
WesleyMFrederickSquashes Git feature-branch history into a single commit when merging to main.
