speckit-worktree-clean

Git worktrees consume disk space because each worktree creates a separate working directory with its own files. This skill identifies stale or merged worktrees and removes them after user confirmation to safely reclaim storage while preserving active development branches.

To remove a merged worktree without losing uncommitted changes, this skill performs per-worktree checks for uncommitted modifications before deletion. It presents a plan and only removes worktrees that are safely merged or orphaned, ensuring active work is preserved.

Git worktree cleanup works with spec-kit style projects by targeting the .worktrees directory. The skill validates prerequisites, identifies merged or orphaned worktrees within that structure, and executes a safe removal plan followed by a final git prune.

The best way to manage git worktree branch maintenance is to use a skill that automatically identifies active, stale, and merged worktrees. It provides a safe default that removes only merged and orphaned entries, generating a cleanup plan for confirmation before any deletion occurs.

You can remove all git worktrees during repository maintenance by using the all-clean scenario, but the skill enforces safety checks first. It validates prerequisites, checks for uncommitted changes per worktree, and requires user confirmation before executing the final prune.

Git worktree prune can leave stale directories behind when worktrees are not properly removed or uncommitted changes exist. This skill handles stale, merged, and orphaned scenarios by performing per-worktree checks and generating a safe deletion plan before the final prune.