gsd-remove-workspace

You can safely remove a git worktree by executing `git worktree remove` for each member repository before deleting the workspace directory. This process requires prior confirmation and refuses to execute if any member repo contains uncommitted changes.

If a member repository has uncommitted changes, the workspace deletion is refused. This guardrail prevents unsafe deletions and ensures the repository is not left in a broken or dirty state during worktree cleanup.

Cleaning up multiple git worktrees across member repositories requires a workspace removal tool that iterates through each member repo. It runs `git worktree remove` for each one and then deletes the main workspace directory after user confirmation.

You should use a dedicated workspace removal tool when managing multiple member repositories under a worktree strategy. Manual deletion leaves broken states, whereas a dedicated tool enforces safety checks, validates uncommitted changes, and properly cleans associated worktrees.

Yes, workspace deletion requires explicit user confirmation before proceeding. Once confirmed, the process validates repository states, removes associated git worktrees for each member repo, and finally deletes the specified workspace directory.