gsd-remove-workspace

To safely remove a git worktree, use an automated cleanup skill that validates repository states for uncommitted changes before deleting the workspace directory and executing git worktree removal commands to prevent data loss.

When deleting a workspace with uncommitted changes, the removal process performs safety checks and refuses to purge the isolated workspace, preventing accidental data loss by ensuring local environments remain consistent.

To clean up task-scoped workspaces after a feature branch merges, invoke the automated cleanup process by providing the workspace name to instantly purge the isolated workspace and restore your local file system state.

Yes, you can automate multi-repo worktree cleanup by orchestrating the removal of workspace directories and associated git worktrees, solving the challenge of manually cleaning complex environments to ensure local consistency.

The best way to delete a git-stacks workspace without losing data is using a cleanup tool that validates repository states and blocks deletion of workspaces containing uncommitted changes before executing removal commands.

Manual git worktree cleanup often fails to maintain environment hygiene because it lacks automated safety checks for uncommitted changes and does not orchestrate complete removal of task-scoped workspace directories and associated worktrees.