worktree-context

Worktree-context centralizes worktree logic by detecting in-worktree status, retrieving worktree info (path, branch, type), and generating context blocks for agents. This eliminates duplicative inline worktree commands across your multi-branch workflow, exposing unified JSON output with fields like is_worktree, worktree_path, branch, and worktree_slug.

Yes. Worktree-context supports create, info, and context commands to automatically set up worktrees for features or epics and generate Task() agent prompts with standardized context blocks, reducing manual setup and ensuring consistent worktree metadata across your automation workflows.

Worktree-context outputs JSON with is_worktree status, worktree_path, root_path, branch name, worktree_type, and worktree_slug. It also supports commands to retrieve relative paths, extract slugs, and generate formatted context blocks for agent prompts.

Use the context command to generate compact prompt blocks containing worktree metadata. These blocks embed current worktree state—path, branch, type—directly into agent instructions, enabling agents to make branch-aware decisions without querying Git separately.

Yes. Worktree-context is designed for multi-branch Git workflows and integrates with existing worktree structures. It detects current worktree state, manages worktree-specific paths, and provides state persistence integration without requiring changes to your existing Git setup.

Worktree-context includes in-worktree, info, create, path, context, relative-path, and extract-slug commands. These handle worktree detection, metadata retrieval, creation, path resolution, and context block generation for agent integration.