gsd-remove-workspace

Remove a GSD workspace and clean up associated git worktrees.

264|11|Updated Apr 25, 2026

Search Tags:#cleanup #git worktree #repository management #workspace removal #task teardown

Ready to run

npx skills add https://github.com/coco-research/coco --skill gsd-remove-workspace-coco-research

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-remove-workspace
Source: https://github.com/coco-research/coco/tree/main/systems/gsd/skills/gsd-remove-workspace
Command: npx skills add https://github.com/coco-research/coco --skill gsd-remove-workspace-coco-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes a completed GSD workspace without leaving behind stale worktrees or partially cleaned repository state.

Core Features & Use Cases

Workspace Teardown: Confirms before deleting the workspace directory so accidental removals are avoided.
Worktree Cleanup: Removes linked git worktrees for each member repository first when the workspace uses a worktree strategy.
Safety Guardrails: Refuses to proceed if any repository contains uncommitted changes, preventing data loss.
Use Case: Use it when a project workspace is finished and you need to cleanly reclaim local disk space and repository state.

Quick Start

Remove the workspace named alpha and confirm that all associated worktrees are cleaned up safely.

Frequently Asked Questions about gsd-remove-workspace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I safely remove git worktrees when cleaning up a multi-repository 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.

What happens if I try to remove a workspace with uncommitted changes?▼

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.

How do I clean up stale worktrees after finishing a project task?▼

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.

Does workspace removal require manual confirmation before deleting directories?▼

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.

When should I use an automated workspace teardown process instead of manual deletion?▼

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.