fleet-tidying-worktrees

To safely prune git worktrees across multiple repos, run a fleet-wide tidying routine that defaults to dry-run mode. It conservatively removes only fully merged or remotely deleted worktrees with no unpushed changes, preserving active ones. Apply changes by passing --fix.

The safest way to clean up spent git worktrees before a cascade wave is using a conservative, no-prompt fleet maintenance tool. It automatically preserves dirty worktrees or those with unpushed commits to protect potential parallel session live work.

Fleet worktree pruning does not remove active worktrees with unpushed commits. A defined removability predicate ensures that dirty worktrees or those carrying unpushed changes are always kept, targeting only fully merged or remotely gone worktrees.

Yes, you can preview which git worktrees will be deleted because the fleet tidying routine defaults to a dry-run mode. This allows you to review safe removals across your repositories before executing the routine again with --fix to apply changes.

You should avoid automated worktree pruning across repositories when parallel sessions might have live work. The conservative predicate keeps dirty worktrees and those with unpushed commits, but manual review is advised if session isolation is unclear.