worktrees

Create isolated git worktrees with automatic directory placement and environment setup.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/ckallum/calsuite --skill worktrees-ckallum
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktrees
Source: https://github.com/ckallum/calsuite/tree/main/skills/worktrees
Command: npx skills add https://github.com/ckallum/calsuite --skill worktrees-ckallum

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing multiple feature workstreams can clutter your main repository and complicate dependency management. This Skill creates isolated git worktrees to keep your primary workspace clean while enabling parallel work.

Core Features & Use Cases

  • Auto-create isolated git worktrees for a given branch, with automatic parent-child directory layout next to the repository root.
  • Detect project type and run appropriate setup commands for common ecosystems (npm/yarn, cargo, pip, go modules, etc.).
  • Safety checks to prevent creating worktrees inside the repo without gitignore coverage and to avoid overwriting existing paths.
  • Clear reporting of the new worktree status: branch, location, base, and setup results.
  • Use cases include starting a feature off origin/main, parallel experiments, and clean separation of work across multiple teams.

Quick Start

Use the worktrees skill to spin up a new feature worktree by specifying a branch name; it will auto-detect the project setup and place the worktree alongside the repository.

Frequently Asked Questions about worktrees

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

FAQPage Schema
How do I create isolated git worktrees for parallel feature development?

To create isolated git worktrees, use this skill to automatically spawn a new worktree for a specified branch. It places the directory alongside your main repository root and runs ecosystem-specific setup commands to enable clean parallel development without cross-branch contamination.

Why does managing multiple feature branches clutter my main repository?

Managing multiple feature branches in a single working directory causes clutter because switching branches overwrites file states and complicates dependency management. Isolated git worktrees solve this by providing separate directories for each branch, keeping your primary workspace clean.

Can I set up isolated worktrees for Python, Go, and React projects automatically?

Yes, you can set up worktrees for Python, Go, and React projects automatically. The skill detects project manifests and runs the appropriate environment setup commands, including npm, yarn, pip, cargo, and go modules, ensuring each worktree has its own isolated dependencies.

What is the best way to prevent cross-branch contamination when switching git features?

The best way to prevent cross-branch contamination is using isolated git worktrees. This skill creates separate parent-child directory layouts for each feature branch, ensuring that file changes and installed dependencies remain completely separated from your main repository.

Are there safety checks to avoid overwriting existing paths when creating a git worktree?

Yes, there are safety checks to avoid overwriting existing paths. The skill validates that new worktrees are not created inside the main repository without gitignore coverage and prevents operations that would overwrite existing directories, ensuring safe parallel development.