skills.rest
martiendejong
martiendejongCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

allocate-worktree

Allocate an isolated Git worktree with conflict detection and seat tracking.

1|Updated Jan 11, 2026
Search Tags:#automation#git#multi-agent#worktree#branch-management#conflict-detection
One-click install
npx skills add https://github.com/martiendejong/autonomous-dev-system --skill allocate-worktree
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: allocate-worktree
Source: https://github.com/martiendejong/autonomous-dev-system/tree/main/.claude/skills/allocate-worktree
Command: npx skills add https://github.com/martiendejong/autonomous-dev-system --skill allocate-worktree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Allocate a worker agent worktree for code editing following zero-tolerance rules. Use when starting code work, needing isolated workspace, or beginning feature implementation. Enforces multi-agent conflict detection and proper seat allocation.

Core Features & Use Cases

  • Isolated worktrees per task to prevent cross-task interference.
  • Enforces zero-tolerance conflict checks and proper seat allocation governance.
  • Supports audit logging and pool/instance tracking for governance.

Quick Start

Perform a conflict-aware allocation by following the protocol to mark a seat as BUSY, create the required worktrees, and log the activity.

Frequently Asked Questions about allocate-worktree

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

FAQPage Schema
How do I create isolated Git worktrees for multi-agent coding tasks?▼

Isolated Git worktrees for multi-agent coding are allocated by marking a seat as BUSY, creating required worktrees, and logging activity. This enforces zero-tolerance conflict checks and prevents cross-task interference.

What is multi-agent conflict detection in shared Git workspaces?▼

Multi-agent conflict detection in shared Git workspaces is a pre-allocation check that verifies the base repo on develop and detects clashes before synchronized branch creation, ensuring zero-tolerance isolation.

How do I manage seat allocation in a shared multi-agent development environment?▼

Seat allocation in a shared environment is managed by marking seats as BUSY and logging activity to update pool and instances maps. This maintains strict governance over synchronized branch creation and isolated workspaces.

Can I create paired Git worktrees for multi-repo feature branches?▼

Yes, paired Git worktrees can be created for multi-repo feature branches. The allocation process supports paired worktrees when required, ensuring synchronized branch creation across repositories while enforcing conflict detection.

When do I need zero-tolerance conflict checks for Git worktree allocation?▼

Zero-tolerance conflict checks for Git worktree allocation are needed when starting code work or feature implementation in multi-agent environments. They enforce strict seat management and prevent cross-task interference in isolated workspaces.

Related Skills

Explore More Software Engineering Skills→
ambroselittleambroselittle

super-work

Creates Superset workspaces by resolving repo, branch, and environment context.

Community
Advanced
martiendejongmartiendejong
1

worktree-status

Assess worktree pool capacity and active allocations across repositories.

Community
Intermediate
jankneumannjankneumann
4

worktree

Manage per-change Git worktrees with a central registry and openspec naming.

Community
Advanced
iani-kuliiani-kuli

using-git-worktrees

Create and manage isolated git worktrees for feature development.

Community
Advanced