qsd-remove-workspace

Remove a qsd workspace and detach its associated worktrees.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/thecomputer07/qsd --skill qsd-remove-workspace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qsd-remove-workspace
Source: https://github.com/thecomputer07/qsd/tree/main/skills/qsd-remove-workspace
Command: npx skills add https://github.com/thecomputer07/qsd --skill qsd-remove-workspace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Remove a qsd workspace and clean up related worktrees to keep repositories tidy and up-to-date.

Core Features & Use Cases

  • Safely remove a workspace directory and detach all associated worktrees
  • Validate there are no uncommitted changes in involved repos before deletion
  • Execute per-repo git worktree removals followed by workspace cleanup

Quick Start

Remove the target workspace by name to delete its directory and detach all worktrees.

Frequently Asked Questions about qsd-remove-workspace

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

FAQPage Schema
How do I safely remove a git worktree and clean up my workspace?

To safely remove a git worktree and workspace, you must validate that no uncommitted changes exist in the involved repositories. This skill executes per-repo worktree detachments followed by workspace directory cleanup to keep repositories tidy.

What happens if I try to delete a workspace with uncommitted changes in git worktrees?

Deleting a workspace with uncommitted changes triggers a safety validation check. The removal process requires explicit confirmation to prevent accidental data loss, ensuring your local environment changes are reviewed before any worktrees are detached and directories are deleted.

Can I automate cleanup of git worktrees across multiple repos managed in one workspace?

You can automate cleanup of git worktrees across multiple repos managed within a single workspace. The removal process operates across all associated repositories, executing per-repo git worktree detachments before finalizing the workspace directory deletion.

Do I need to manually detach git worktrees before removing my repository workspace?

You do not need to manually detach git worktrees before removing your repository workspace. The process handles per-repo worktree removals automatically, followed by the final workspace cleanup, provided explicit confirmation is given for the deletion.

Why does workspace removal require explicit confirmation before deleting directories?

Workspace removal requires explicit confirmation to enforce safety validation and avoid accidental deletions. This precaution ensures that associated git worktrees are only detached and local directories deleted after verifying no uncommitted changes remain in the repositories.