worktree

Create, list, and clean up isolated git worktrees with safety checks.

1|Updated May 18, 2026

Search Tags:#git #cleanup #worktree #branch management #parallel development #workspace isolation

Ready to run

npx skills add https://github.com/linenoize/topia --skill worktree-linenoize

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of managing separate git workspaces when multiple streams of work need to happen in parallel, or when an experiment must stay isolated from the main tree.

Core Features & Use Cases

Create isolated workspaces: Spins up dedicated worktrees for feature streams, experiments, or agent-assigned tasks.
Manage lifecycle safely: Lists active worktrees, checks merge state, and cleans up stale branches and paths with guardrails.
Enforce team conventions: Uses a consistent .claude/worktrees location, Topia branch naming, and limits active worktrees to reduce chaos.
Use case: A team can split three independent features into separate worktrees, develop them in parallel, and remove them cleanly after merge.

Quick Start

Ask the worktree skill to create a new isolated worktree named stream-a from the current branch for parallel development.

Frequently Asked Questions about worktree

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

FAQPage Schema

How do I create isolated git workspaces for parallel feature development?▼

Git worktree management supports parallel feature streams by creating dedicated worktrees from the current branch, enforcing .claude/worktrees placement and Topia branch naming to isolate development without disturbing the main tree.

What is the safest way to clean up stale git worktrees after merging?▼

Cleaning up stale git worktrees safely requires checking merge state and uncommitted changes before removal. Safety guardrails verify merge completion and prevent data loss when cleaning up stale branches and paths.

Can I manage multiple git worktrees for separate team-assigned tasks?▼

Yes, you can manage multiple git worktrees for team-assigned tasks, but the system enforces active-worktree limits to reduce chaos and maintain organized workspace isolation across independent feature streams.

How do I list active git worktrees and check their merge state?▼

Listing active git worktrees displays all current isolated workspaces and checks their merge state, allowing you to verify which branches are ready for cleanup or still require integration before safe removal.

Does git worktree branch management prevent uncommitted changes from being lost?▼

Git worktree branch management includes safety checks for uncommitted changes before cleanup. These guardrails prevent data loss by verifying merge state and uncommitted modifications prior to removing stale branches.