gsd-workspace

Create, list, and remove isolated GSD workspace environments.

Updated May 22, 2026
One-click install
npx skills add https://github.com/yusaduymaz/loexai --skill gsd-workspace-yusaduymaz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-workspace
Source: https://github.com/yusaduymaz/loexai/tree/main/.codex/skills/gsd-workspace
Command: npx skills add https://github.com/yusaduymaz/loexai --skill gsd-workspace-yusaduymaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of juggling isolated development workspaces by guiding you through workspace creation, discovery, and cleanup with consistent rules and safeguards.

Core Features & Use Cases

  • Workspace Creation: Set up a new isolated workspace for a specific repo, branch, or path when you need a safe environment for focused work.
  • Workspace Listing: Review active workspaces and their status so you can quickly understand what is running and where.
  • Workspace Removal: Cleanly remove a workspace and its related worktree state when the task is finished.
  • Use Case: A developer can spin up a dedicated workspace for a feature branch, inspect other active workspaces, and later remove the one that is no longer needed.

Quick Start

Use the gsd-workspace skill to create, list, or remove a workspace by providing the appropriate mode and any required details.

Frequently Asked Questions about gsd-workspace

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

FAQPage Schema
How do I create an isolated Git worktree workspace for a feature branch?

You can create an isolated workspace by providing the repository path and branch details, which sets up a branch-scoped environment for focused development work without disturbing your main repository.

What is the best way to list and review active development workspaces?

Listing active development workspaces requires using the workspace listing mode, which reviews running environments and their status so you can quickly understand what is active and where it is located.

How do I cleanly remove a workspace and its related worktree state?

Cleanly remove a workspace by triggering removal mode, which handles directory cleanup and confirmation safeguards to delete the worktree state without prematurely writing artifacts or losing workflow progress.

Do I need any external dependencies to manage repository workspace lifecycle tasks?

No external dependencies are required for repository workspace lifecycle tasks. The environment handles branch-scoped setup, status review, and cleanup natively using built-in mode-based routing and confirmation handling.

When should I use branch-scoped workspace environments instead of a single repository?

Branch-scoped workspace environments are ideal when you need isolated paths for parallel development across new or existing projects, ensuring safe, focused work without interfering with your main repository state.

Why does workspace directory cleanup require confirmation handling and mode-based routing?

Workspace directory cleanup requires confirmation handling and mode-based routing to preserve active workflows and prevent premature artifact writing, ensuring worktree state is only removed when explicitly verified.