worktree

Automates Git worktree management for ticket-based development with branch safety checks and optional dry-run support.

1|Updated Jul 24, 2025

Search Tags:#automation #git #development #cli #worktree #ticket

Ready to run

npx skills add https://github.com/tarrragon/book_overview_v1 --skill worktree-tarrragon

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: worktree
Source: https://github.com/tarrragon/book_overview_v1/tree/main/.claude/skills/worktree
Command: npx skills add https://github.com/tarrragon/book_overview_v1 --skill worktree-tarrragon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill automates the management of Git worktrees for ticket-based development, enabling isolated, parallel work environments per ticket and reducing setup friction.

Core Features & Use Cases

Create and manage per-ticket worktrees to keep workspaces isolated.
View status, list all worktrees, and monitor uncommitted changes across environments.
Respond to mentions of /worktree or related terms to trigger quick environment setup.

Quick Start

Create a new worktree for a ticket by invoking the create command with the ticket ID.

Frequently Asked Questions about worktree

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

FAQPage Schema

How do I automate Git worktree creation for individual tickets?▼

Automating Git worktree creation for tickets requires invoking the create command with a specific ticket ID to instantly isolate a parallel development environment. This workflow applies safety checks for existing paths and branch conflicts to prevent errors during automated environment setup.

What is the best way to manage isolated Git worktrees for parallel development?▼

Managing isolated Git worktrees for parallel development involves using a frontmatter-driven entry point to create, inspect, and list environments. This approach reduces setup friction by automatically applying safety checks for existing paths and branch conflicts before establishing each workspace.

How does a ticket-based Git worktree setup handle branch conflicts?▼

Ticket-based Git worktree setup handles branch conflicts by implementing safety checks that verify existing paths and branch states before creating new environments. It also supports an optional dry-run mode, allowing developers to preview operations and avoid conflicts without modifying the actual repository.

Can I list all Git worktrees and monitor uncommitted changes across environments?▼

You can list all Git worktrees and monitor uncommitted changes across environments using the dedicated list and status commands. These features allow developers to view the current state of every isolated workspace, ensuring no work is lost across parallel ticket branches.

Do I need to manually run commands to set up a Git worktree for every new ticket?▼

You do not need to manually run commands to set up a Git worktree for every new ticket. The system automatically responds to mentions of /worktree or related terms, triggering quick environment setup and applying necessary safety checks without manual intervention.