dispatch-worktree

Create and remove ephemeral git worktrees for isolated agent dispatches.

3|2|Updated May 12, 2026
One-click install
npx skills add https://github.com/kriscendobot/garden --skill dispatch-worktree
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dispatch-worktree
Source: https://github.com/kriscendobot/garden/tree/main/skills/dispatch-worktree
Command: npx skills add https://github.com/kriscendobot/garden --skill dispatch-worktree

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the problem of managing concurrent, isolated development environments for automated agents, preventing cross-contamination of git state and ensuring consistent bot identity across multiple tasks.

Core Features & Use Cases

  • Ephemeral Worktree Management: Automatically creates and tears down isolated git worktrees for specific agent dispatches.
  • Identity Pinning: Enforces consistent bot identity (name and email) within sub-worktrees, preventing accidental commits under the maintainer's identity.
  • Use Case: When an agent needs to work on a specific PR, this skill prepares a clean, detached-HEAD environment containing the garden, journal, and project code, ensuring the agent can fetch and rebase without affecting the orchestrator's state.

Quick Start

Invoke the dispatch-prepare script with the target role and purpose slug to initialize a new isolated worktree environment for your agent task.

Frequently Asked Questions about dispatch-worktree

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

FAQPage Schema
How do I manage isolated git worktrees for concurrent automated agents?

Isolated git worktrees for concurrent automated agents are managed by creating and tearing down ephemeral environments using detached-HEAD states. This ensures agents can fetch and rebase code without cross-contaminating the orchestrator's git state.

Why do my automated agents commit under the wrong git identity in isolated worktrees?

Automated agents commit under the wrong git identity in isolated worktrees due to missing identity pinning. Enforcing consistent bot name and email pinning within sub-worktrees prevents accidental commits under the maintainer's identity.

How do I prevent git state collisions when orchestrating multiple concurrent agent tasks?

Git state collisions during concurrent agent orchestration are prevented by dispatching agents into detached-HEAD worktrees. This isolates the garden, journal, and project checkouts, ensuring tasks operate independently without affecting the main repository.

What's the best way to prepare an ephemeral environment for an automated agent dispatch?

The best way to prepare an ephemeral environment for an automated agent dispatch is invoking a prepare script with a target role and purpose slug. This initializes a clean, isolated worktree containing the garden, journal, and project code.

Does dispatch-worktree work within a garden repository architecture?

Yes, dispatch-worktree operates specifically within the garden repository architecture. It provides dedicated checkouts for the garden, journal, and project code to support concurrent agent tasks while maintaining isolated git states.