Skip to content
Back to search

worktree-manager-skill

a claude code skill for effortless worktree management

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/wirasm--worktree-manager-skill/badge.svg)](/listings/wirasm--worktree-manager-skill)

HTML

<a href="/listings/wirasm--worktree-manager-skill"><img src="/api/listings/wirasm--worktree-manager-skill/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Clone this repo into your Claude skills directory:

# Global installation (available in all projects)
git clone git@github.com:Wirasm/worktree-manager-skill.git ~/.claude/skills/worktree-manager

# Or project-specific (available only in that project)
git clone git@github.com:Wirasm/worktree-manager-skill.git .claude/skills/worktree-manager

Restart Claude Code after installation.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 89 lines · 1 finding marked

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Worktree Manager
  2. ![Worktree Manager](cover.png)
  3. A Claude Code skill for managing parallel development environments using git worktrees.
  4. ## Installation
  5. Clone this repo into your Claude skills directory:
  6. ```bash
  7. # Global installation (available in all projects)
  8. git clone git@github.com:Wirasm/worktree-manager-skill.git ~/.claude/skills/worktree-manager
  9. # Or project-specific (available only in that project)
  10. git clone git@github.com:Wirasm/worktree-manager-skill.git .claude/skills/worktree-manager
  11. ```
  12. Restart Claude Code after installation.
  13. ## Configuration
  14. Edit `~/.claude/skills/worktree-manager/config.json` to customize:
  15. ```json
  16. {
  17. "terminal": "ghostty",
  18. "shell": "bash",
  19. "claudeCommand": "claude --dangerously-skip-permissions",
  20. "portPool": { "start": 8100, "end": 8199 },
  21. "portsPerWorktree": 2,
  22. "worktreeBase": "~/tmp/worktrees"
  23. }
  24. ```
  25. | Setting | Default | Description |
  26. | ------------------ | --------------------------------------- | ----------------------------------------------------------------------------------------- |
  27. | `terminal` | `ghostty` | Terminal to open agents in (`ghostty`, `iterm2`, `tmux`, `wezterm`, `kitty`, `alacritty`) |
  28. | `shell` | `bash` | Shell to use (`bash`, `zsh`, `fish`) |
  29. | `claudeCommand` | `claude --dangerously-skip-permissions` | Command to launch Claude Code |
  30. | `portPool` | `8100-8199` | Port range for dev servers |
  31. | `portsPerWorktree` | `2` | Ports allocated per worktree (e.g., API + frontend) |
  32. | `worktreeBase` | `~/tmp/worktrees` | Where worktrees are created |
  33. ## What This Does
  34. **The problem:** You're working on a feature when an urgent bug comes in. You have uncommitted changes, half-finished work, a dev server running. Switching branches means stashing everything, stopping servers, and losing your flow. When you come back, you have to reconstruct your entire environment.
  35. **The solution:** Git worktrees let you have multiple branches checked out simultaneously in separate directories. Each is a complete, independent working copy. But setting them up manually is tedious—you need to create the worktree, copy environment files, install dependencies, configure ports so nothing conflicts, and remember to clean everything up later.
  36. **This skill automates all of that.** Just say:
  37. > "Spin up worktrees for feature/auth and fix/payment-bug"
  38. Claude will:
  39. 1. Create isolated worktree directories for each branch
  40. 2. Copy necessary files (`.env`, `.agents/`, etc.)
  41. 3. Install dependencies automatically
  42. 4. Allocate unique ports so dev servers don't conflict
  43. 5. Open new terminal windows with Claude Code agents ready to work
  44. All worktrees are tracked in a global registry, so you can check status across all your projects and clean up when branches are merged.
  45. **Why it's valuable:**
  46. - **Parallel development** — Work on multiple features simultaneously with dedicated Claude agents
  47. - **Zero context switching** — Each worktree maintains its own state, dependencies, and running servers
  48. - **No port conflicts** — Global port allocation ensures dev servers across projects never collide
  49. - **Easy cleanup** — One command removes worktrees, kills servers, and releases ports when you're done
  50. ## Usage
  51. The skill activates automatically when you mention worktrees:
  52. - "Create a worktree for feature/dark-mode"
  53. - "Spin up 3 worktrees for these tickets"
  54. - "What's the status of my worktrees?"
  55. - "Clean up the auth worktree"
  56. ## Requirements
  57. - `jq` — Install with `brew install jq` (macOS) or `apt install jq` (Linux)
  58. - `git` — For worktree operations
  59. - A supported terminal application
  60. ## License
  61. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.