gsd-remove-workspace

To safely remove a git worktree, the Skill checks for uncommitted changes across all member repositories and refuses to proceed if any are found, ensuring local changes are not accidentally lost during workspace cleanup.

The best way to clean up multiple git worktrees is to iterate through each member repository and run git worktree remove individually, preventing dangling worktrees while prompting for explicit confirmation before deleting workspace files.

To delete a stale local workspace spanning multiple git repositories, the Skill performs confirmation prompts, verifies no uncommitted changes exist, and executes git worktree remove for each member repository to reclaim disk space.

Yes, the workspace cleanup process refuses to proceed if any member repository contains uncommitted changes, acting as a safety check to prevent accidental data loss before removing workspace directories and git worktrees.

You should use a worktree-aware cleanup script when preparing to delete or recreate a workspace that uses the git worktree strategy across multiple repositories, as manual deletion often leaves dangling worktrees that require additional git maintenance.