gsd-remove-workspace

To safely remove git worktrees during workspace cleanup, you must first ensure all member repositories have no uncommitted changes. The system then executes git worktree remove for each repository before deleting the workspace directory, requiring explicit confirmation to prevent accidental data loss.

Workspace removal refuses to proceed if any member repository contains uncommitted changes. This safety guardrail prevents data loss by blocking the git worktree remove process and workspace deletion until all local modifications are committed or discarded.

Cleaning up stale worktrees after a finished task requires running git worktree remove for each linked member repository. This task teardown process ensures no stale worktree references remain before the workspace directory is safely deleted to reclaim local disk space.

Yes, workspace removal requires explicit confirmation before deleting the workspace directory. This prevents accidental removals, ensuring the git worktree cleanup and subsequent directory deletion only executes when intentionally approved by the user.

Automated workspace teardown is necessary for multi-repository GSD setups using a worktree strategy. It ensures safe repository state by verifying no uncommitted changes exist and systematically removing linked worktrees, which manual directory deletion bypasses.