branch-worktree

Create a named git worktree and color-coded VSCode window for isolated development tasks.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ryan-mahoney/ryan-llm-skills --skill branch-worktree
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: branch-worktree
Source: https://github.com/ryan-mahoney/ryan-llm-skills/tree/main/skills/branch-worktree
Command: npx skills add https://github.com/ryan-mahoney/ryan-llm-skills --skill branch-worktree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a git worktree with a structured branch name derived from a loose description, configure the environment, color-code the VSCode window, and open it.

Core Features & Use Cases

  • Derive a deterministic branch slug from a free-text description, optionally using an issue number as prefix.
  • Create and manage a worktree under ~/.worktrees to keep the main repository clean and organized.
  • Apply a deterministic VSCode color theme to the work window for easy visual distinction.
  • Open the new worktree in a separate VSCode window ready for development and testing.

Quick Start

Describe the work to perform and the tool will create a dedicated worktree and open it in VSCode.

Frequently Asked Questions about branch-worktree

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

FAQPage Schema
How do I create a git worktree with a structured branch name from a text description?

To create a git worktree with a structured branch name, this tool derives a deterministic branch slug from free-text descriptions, optionally prefixing an issue number, and sets up an isolated development workspace.

Can I color-code my VSCode windows to visually distinguish different git worktrees?

Yes, you can color-code VSCode windows for different git worktrees. This tool applies a deterministic VSCode color theme to each new work window, allowing easy visual distinction between isolated development tasks.

How do I keep my main repository clean when working on multiple isolated feature branches?

To keep your main repository clean when working on multiple isolated features, this tool creates and manages dedicated worktrees under a structured ~/.worktrees path rather than cluttering the primary directory.

Does this worktree automation tool enforce non-main branches for development?

Yes, this worktree automation tool enforces non-main branches for development. It ensures you do not accidentally create worktrees directly on the main branch, protecting your primary branch state.

What is the best way to set up an independent workspace for a new feature issue in VSCode?

The best way to set up an independent workspace for a new feature issue is using git worktree automation that creates a dedicated path, applies a color theme, and opens a separate VSCode window ready for development.

Are there limitations to using git worktrees for multi-task development workflows?

A limitation of using git worktrees for multi-task workflows is that this tool strictly enforces non-main branches and stores paths under ~/.worktrees, requiring adherence to this specific directory structure and branch policy.