doey-worktree

Isolates a team window in a git worktree for tmux-based development.

6|2|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/FRIKKern/doey --skill doey-worktree
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doey-worktree
Source: https://github.com/FRIKKern/doey/tree/main/.claude/skills/doey-worktree
Command: npx skills add https://github.com/FRIKKern/doey --skill doey-worktree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines isolation of active team windows when working with multiple git worktrees and tmux sessions, preventing cross-project interference.

Core Features & Use Cases

  • Session isolation: creates or reattaches a team window within a dedicated git worktree.
  • Safe teardown: returns from isolation by removing the worktree context and restoring previous environment.
  • State management: validates active sessions, avoids busy workers, and preserves session state across transitions.

Quick Start

Run the doey-worktree skill to isolate a team window in a git worktree and return it when finished.

Frequently Asked Questions about doey-worktree

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

FAQPage Schema
How do I isolate a tmux session in a git worktree to prevent cross-project interference?

To isolate a tmux session in a git worktree, you can create or reattach a dedicated team window within the worktree, keeping team contexts separated without affecting your main workspace.

What is the best way to manage multiple git worktrees in tmux for team workflows?

Managing multiple git worktrees in tmux involves isolating active team windows in separate worktrees, validating active sessions, and ensuring safe teardown to restore your previous environment state.

How do I safely remove a git worktree and return to my main tmux workspace?

To safely remove a git worktree and return to your main tmux workspace, the teardown process removes the worktree context, checks for busy workers, and restores the previous session state.

Can I use tmux session management to preserve state across multiple git worktree transitions?

Yes, tmux session management can preserve state across git worktree transitions by validating active sessions, avoiding busy workers, and safely returning projects without losing your environment configuration.

Does git worktree isolation work with existing tmux session configurations?

Git worktree isolation works with tmux by parsing existing sessions and loading configurations to create or reattach team windows, ensuring your team contexts remain separated and easily recoverable.

Why should I use git worktrees instead of cloning repositories for isolated team windows?

Git worktrees allow you to isolate team windows within a single repository, preventing cross-project interference while avoiding the overhead of managing multiple clones and preserving session state across transitions.