ywc-worktrees

Automates creation, auditing, and pruning of Git worktrees.

8|1|Updated May 13, 2026
One-click install
npx skills add https://github.com/yongwoon/ywc-agent-toolkit --skill ywc-worktrees
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ywc-worktrees
Source: https://github.com/yongwoon/ywc-agent-toolkit/tree/main/claude-code/skills/ywc-worktrees
Command: npx skills add https://github.com/yongwoon/ywc-agent-toolkit --skill ywc-worktrees

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, bash, and includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the manual overhead and potential for error when managing isolated Git worktrees, ensuring consistent workspace isolation and preventing stale metadata or path collisions.

Core Features & Use Cases

  • Lifecycle Management: Automates the creation, auditing, and pruning of Git worktrees to maintain a clean development environment.
  • Priority Resolution: Enforces a standardized path resolution chain (.worktrees/ > CLAUDE.md > --root) to ensure predictable workspace locations across projects.
  • Use Case: When running parallel tasks, use this Skill to automatically provision a dedicated worktree for each task and clean up all associated branches and metadata once the task is complete.

Quick Start

Use the ywc-worktrees skill to create a new worktree for the current task using the specified base branch.

Frequently Asked Questions about ywc-worktrees

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

FAQPage Schema
How do I automate Git worktree cleanup and creation for parallel tasks?

Git worktree lifecycle management automates creation, auditing, and pruning to provide isolated development workspaces for parallel task execution. It ensures consistent path resolution, removes stale metadata, and safely deletes local branches after task completion.

What is the best way to manage stale Git worktree metadata and path collisions?

Automated worktree pruning is the best way to manage stale Git worktree metadata and path collisions. By enforcing a standardized path resolution chain, it ensures predictable workspace locations and removes stale metadata safely.

Do I need bash and git installed to automate worktree lifecycle management?

Yes, you need both git and bash installed to automate worktree lifecycle management. These dependencies are required to execute the scripts that handle worktree creation, metadata auditing, and safe local branch deletion.

How does path resolution work when creating a new Git worktree?

Path resolution when creating a Git worktree works by enforcing a priority chain: .worktrees/ directory first, then CLAUDE.md, and finally the --root flag. This standardized chain ensures predictable workspace locations across projects.

When should I use Git worktrees instead of cloning multiple repositories?

You should use Git worktrees instead of cloning when you need isolated development workspaces for parallel task execution without duplicating repository history. Worktrees share a single repository, simplifying branch management and post-merge cleanup workflows.