gsd-new-workspace

Creates isolated Git workspace directories with configurable repositories, paths, and branch strategies.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/GenproMM/MMLab_TOOLS --skill gsd-new-workspace-genpromm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-new-workspace
Source: https://github.com/GenproMM/MMLab_TOOLS/tree/main/.claude/skills/gsd-new-workspace
Command: npx skills add https://github.com/GenproMM/MMLab_TOOLS --skill gsd-new-workspace-genpromm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a streamlined way to create isolated workspaces for Git repositories, ensuring that each workspace maintains its own state and planning directory.

Core Features & Use Cases

  • Isolated Workspace Creation: Generates a workspace directory with copies of specified Git repositories.
  • Flexible Repository Handling: Supports worktree or clone strategies for repository handling.
  • Customization Options: Allows customization of workspace name, path, and branch.
  • Use Case: Ideal for parallel development on different branches or collaborative projects where isolation of workspace state is essential.

Quick Start

Run the command: gsd-new-workspace --name <name> --repos repo1,repo2 --path /target --strategy worktree --branch name --auto

Frequently Asked Questions about gsd-new-workspace

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

FAQPage Schema
How do I create an isolated Git workspace for parallel branch development?

You can create an isolated Git workspace by specifying a workspace name, target repositories, and a path. This generates a dedicated directory with independent planning directories, allowing multiple branches to be developed simultaneously without state conflicts.

What is the difference between worktree and clone strategies for repository workspaces?

A worktree strategy links branches as separate working trees within the same Git repository, sharing object storage. A clone strategy creates a fully independent repository copy, completely isolating workspace state from the original repository.

How do I set up a custom workspace path and checkout a specific branch?

You can set up a custom workspace path and checkout a specific branch by providing the target directory location and branch name parameters during workspace creation. This ensures the isolated workspace opens directly with your desired branch checked out.

Do I need special Git permissions to create isolated workspaces?

You need a standard Git environment installed and appropriate repository access permissions to create isolated workspaces. The workspace creation requires read access to the specified repositories to successfully generate copies or worktrees.

Can I include multiple Git repositories in a single isolated workspace?

Yes, you can include multiple Git repositories in a single isolated workspace by specifying a comma-separated list of repository names. The workspace generator will create copies or worktrees for each specified repository within the target path.

When should I use an isolated workspace instead of standard Git branching?

You should use an isolated workspace when you need completely independent planning directories and separate working trees for collaborative projects. Standard Git branching shares a single working directory, while isolated workspaces maintain separate states for each branch.