worktree

Git worktrees isolate feature development by provisioning a dedicated working directory for each change. This Skill orchestrates setup and teardown, keeping your main branch clean and reducing merge conflicts during feature work.

A central registry tracks Git worktrees by storing their state and activity in a JSON file. This mechanism enables features like heartbeat monitoring, pinning, and garbage collection to reclaim space from stale or merged worktrees.

The best way to clean up stale Git worktrees is using the garbage collection command. It identifies and removes merged worktrees, reclaims disk space, and updates the central registry to ensure only active feature directories remain.

Yes, you can apply a custom branch naming scheme using openspec conventions and an optional agent ID suffix. The setup respects explicit branches and environment overrides to ensure consistent branch naming across tools.

You need to pin a Git worktree to prevent it from being removed by garbage collection. Pinning protects active feature directories from automatic cleanup, ensuring your ongoing development work persists in the registry.

No, this worktree automation tool requires no external dependencies. It operates using standard Python scripts to manage your feature branches, allowing you to run the setup command directly to provision a dedicated worktree.