gsd-remove-workspace

Removing a git worktree workspace requires confirming the workspace name. The Skill then iterates through each member repository, removing worktrees individually while guarding against uncommitted changes to prevent data loss.

When removing a multi-repo workspace, the Skill enforces safety by refusing removal if any repository has uncommitted changes. You must commit or stash changes in all member repos before the workspace cleanup can proceed.

Yes, you can automate workspace cleanup for multi-repo git worktree setups. Designed for workspace management workflows, the Skill automates iterating through member repositories and removing their worktrees after user confirmation.

Yes, removing a workspace directory cleans up all associated git worktrees. The Skill removes both the workspace directory and each member repository's worktree, ensuring the multi-repo setup is fully dismantled.

Workspace removal fails when working with git worktrees if any member repository contains uncommitted changes. This safety mechanism prevents accidental loss of uncommitted work during the automated multi-repo cleanup process.