ta wt & ta workspace — Worktree & Workspace Manager

Manage git worktrees and tmux workspaces with status outputs.

1|4|Updated Oct 27, 2014
One-click install
npx skills add https://github.com/rjernst/dotfiles --skill ta-wt-ta-workspace-worktree-workspace-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ta wt & ta workspace — Worktree & Workspace Manager
Source: https://github.com/rjernst/dotfiles/tree/main/claude/skills/ta-wt
Command: npx skills add https://github.com/rjernst/dotfiles --skill ta-wt-ta-workspace-worktree-workspace-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of juggling multiple git worktrees and keeping matching tmux sessions organized, so you can safely review, merge, and clean up branches without manual coordination.

Core Features & Use Cases

  • Worktree management: Create worktrees that track remote branches, list them with enriched status (including ahead/behind and dirty state), remove them safely, and prune merged branches from main.
  • Workspace automation: Create and manage tmux sessions tied to worktree branches (including an optional multi-window layout that runs a Claude agent), attach to sessions by branch, and kill sessions when done.
  • Safe merge workflow: Squash-merge a worktree branch into a target branch (default main) while validating that both worktrees are clean, then remove the source worktree and its tmux workspace to prevent stale state.

Quick Start

Create a worktree-backed tmux workspace for branch "feature-x" by running ta workspace create feature-x.

Frequently Asked Questions about ta wt & ta workspace — Worktree & Workspace Manager

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

FAQPage Schema
How do I automate git worktree and tmux session management together?

Git worktree and tmux session management is automated by creating worktrees that track remote branches and tying matching tmux sessions to them. This coordinated workspace automation allows you to safely review, merge, and clean up branches without manual tmux and git coordination.

What is the safest way to squash merge a git worktree branch into main?

The safest squash merge workflow validates that both the source and target worktrees are completely clean before merging. After successfully squash merging the worktree branch into the target branch, it automatically removes the source worktree and its tmux workspace to prevent stale state.

Can I list git worktrees with ahead/behind status and dirty state?

Listing git worktrees with enriched status, including ahead/behind counts and dirty state, is a supported feature. The structured status output supports both human-readable formats for quick terminal checks and JSON formats for programmatic parsing.

How do I create a tmux workspace with a multi-window layout for a git branch?

Creating a tmux workspace tied to a specific branch sets up an optional multi-window layout that can run a Claude agent. This provides an idempotent session creation process, ensuring the branch-specific tmux environment is consistently ready for development.

How does dirty-state validation work when cleaning up merged branches?

Dirty-state validation checks for uncommitted changes before allowing any cleanup or merge operations to proceed. It enforces safe removal of worktrees and tmux sessions by returning defined exit codes if the worktree is not clean, preventing accidental data loss during branch pruning.

Do I need to manually kill tmux sessions after removing a git worktree?

Manually killing tmux sessions after removing a git worktree is not required. The workspace automation automatically kills the associated tmux session when the worktree is safely removed or after a successful squash merge workflow completes.