rune-worktree

Manages git worktree lifecycle for parallel isolated development workspaces.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/dangvu008/VietTruyen --skill rune-worktree-dangvu008
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rune-worktree
Source: https://github.com/dangvu008/VietTruyen/tree/main/.agents/skills/rune-worktree
Command: npx skills add https://github.com/dangvu008/VietTruyen --skill rune-worktree-dangvu008

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Parallel development streams and experiments often collide in a single working tree, causing branch conflicts and lost work. This Skill creates and manages isolated git worktrees so multiple agents or developers can work simultaneously without touching the main working tree. ## Core Features & Use Cases - Worktree Creation: Creates isolated workspaces under .claude/worktrees/ with rune/-prefixed branches, capped at 3 active worktrees. - Safe Cleanup: Removes worktrees only after checking for uncommitted changes and unmerged branches, with optional force mode and stale worktree pruning. - Listing & Reporting: Lists active rune/* worktrees and emits a structured Worktree Report with status per workspace. - Use Case: A team skill spins up two parallel feature streams; this Skill creates rune/stream-a and rune/stream-b worktrees, then cleans them up after merge without risking uncommitted agent work. ## Quick Start Ask the agent to create an isolated worktree named auth-feature so you can develop it in parallel without affecting the main working tree.

Frequently Asked Questions about rune-worktree

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

FAQPage Schema
How do I create a git worktree for parallel development?

Run git worktree add with a new branch, or invoke this Skill with a name to create .claude/worktrees/<name> on branch rune/<name>. It verifies creation via git worktree list and returns the path and branch.

How do I clean up stale git worktrees safely?

Use the cleanup operation, which checks whether the branch is merged into main before removing the worktree and deleting the branch. Unmerged branches require explicit force confirmation, and git worktree prune handles orphaned entries.

Is there a limit on how many git worktrees I can run at once?

Yes, this Skill enforces a maximum of 3 active rune/* worktrees and refuses new creation beyond that limit. This keeps disk usage and branch sprawl under control during parallel agent work.

What happens if I delete a worktree with uncommitted changes?

The Skill never deletes a worktree with uncommitted changes without user confirmation. It checks branch merge status first and warns when unmerged work exists, requiring force=true to proceed.

When should I use git worktrees instead of switching branches?

Use worktrees when multiple streams must be checked out simultaneously, such as parallel agent tasks or experiments that must not disturb the main tree. Branch switching suits sequential work on a single stream.