worktree

Manage Git worktrees across repos and branches with init, list, switch, cleanup, and status commands.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/julianjab/ia-tools --skill worktree-julianjab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktree
Source: https://github.com/julianjab/ia-tools/tree/main/skills/worktree
Command: npx skills add https://github.com/julianjab/ia-tools --skill worktree-julianjab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Managing parallel workstreams in a single repository is error-prone and slow. This skill provides isolated Git worktrees so teams can develop, review, and hotfix in parallel without switching branches.

Core Features & Use Cases

  • Create and manage isolated worktrees with the commands init, list, switch, cleanup, and status.
  • Supports multi-repo workflows via --repo <path> to create worktrees in sibling repositories while keeping a shared Git metadata set.
  • Includes guidance to carry Claude configuration across worktrees and maintain consistent behavior.

Quick Start

Create a new worktree for a feature by running /worktree init feat/your-branch (optionally with --repo <path> to target another repository).

Frequently Asked Questions about worktree

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

FAQPage Schema
How do I manage Git worktrees for parallel development across multiple branches?

Manage Git worktrees for parallel development by running commands like init, list, switch, cleanup, and status. The tool validates branch names, fetches origins, creates worktrees, and prints a summary to track your isolated workstreams.

What is the best way to work on a hotfix without switching my current Git branch?

Using Git worktrees provides isolated directories for parallel development, letting you hotfix or review code without switching your current branch. This avoids errors and keeps separate workstreams active simultaneously.

Can I create Git worktrees in sibling repositories with a shared metadata set?

Yes, you can target sibling repositories by passing the optional --repo <path> argument during worktree initialization. This supports multi-repo workflows while keeping a shared Git metadata set across the created worktrees.

How do I carry my Claude configuration across different Git worktrees?

The worktree creation process includes copying Claude configuration across worktrees to maintain consistent behavior. This ensures your settings remain synchronized when switching between isolated development environments.

What are the limitations of using Git worktrees for parallel repo automation?

Git worktrees require validating branch names and fetching origins before creation, adding setup overhead. Multi-repo setups require specifying the --repo path each time to maintain the shared Git metadata set correctly across repositories.

How do I clean up and check the status of my Git worktrees?

Check the status of your Git worktrees using the status command and remove unused ones with the cleanup command. The status command prints a summary of your current worktree state across active repos and branches.