worktree-cleanup

To clean up Git worktrees, you can manually remove leftover development tracks and optionally delete their associated branches. This is useful when automatic worktree cleanup fails after a merge.

Removing a Git worktree is safe because the process validates for uncommitted changes and warns about unpushed commits before removal. This prevents accidental data loss during the branch management cleanup.

You can optionally delete associated Git branches during worktree removal. The cleanup process safely manages branch deletion alongside the worktree cleanup to ensure your repository stays organized.

Automatic Git worktree cleanup can fail after a development track is merged, leaving leftover directories. Manual worktree removal resolves this by safely targeting and deleting the remaining worktree files.

Git worktree cleanup updates SQLite state to maintain an audit trail of removed worktrees and branches. This ensures you have a historical record of the branch management and cleanup actions performed.