gsd-remove-workspace

To safely remove a git worktree without losing uncommitted changes, use a tool that checks repository status first. This Skill refuses to proceed if any member repository has uncommitted changes, ensuring no work is lost during workspace cleanup.

The best way to clean up a multi-repo git worktree workspace is to run git worktree remove for each member repository systematically. This Skill automates that process, removing the workspace directory and all associated worktrees after requiring user confirmation.

No, this workspace cleanup tool does not delete files if repositories have pending changes. It includes safeguards that explicitly refuse to proceed with removing worktrees or the workspace directory when uncommitted changes are detected in any member repository.

To delete a GSD workspace directory and its associated worktrees, provide the workspace name and confirm the action. The Skill executes git worktree remove for each member repo and cleans up the workspace directory, surfacing a clear success message upon completion.

Git worktree remove can fail during workspace cleanup if repositories contain uncommitted changes. This Skill prevents this failure by checking for uncommitted changes beforehand and refusing to remove worktrees until those changes are committed or stashed.

Yes, you can remove multiple git worktrees from a workspace at once. This Skill handles workspaces using a git worktree strategy with multiple member repos, running the removal process for each repository and cleaning the workspace directory after user confirmation.