shine-new-workspace

Create isolated workspaces with git repo copies and a .planning directory.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/diShine-digital-agency/SHINE-Code-System --skill shine-new-workspace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shine-new-workspace
Source: https://github.com/diShine-digital-agency/SHINE-Code-System/tree/main/skills/shine-new-workspace
Command: npx skills add https://github.com/diShine-digital-agency/SHINE-Code-System --skill shine-new-workspace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate creating isolated SHINE workspaces that hold copies of specified git repositories (as either worktrees or clones) and an independent .planning directory, enabling clean, repeatable SHINE sessions across multiple projects.

Core Features & Use Cases

  • Multi-repo workspace creation: assemble chosen repos into a single, isolated environment.
  • Independent planning context: includes a dedicated .planning/ directory for each workspace.
  • Flexible strategy: choose between worktree or clone for each repository.
  • Workspace manifest: generates a WORKSPACE.md that records the configuration.
  • Easy switching: cd into the new workspace and run SHINE workflows.

Quick Start

Use shine-new-workspace to create an isolated workspace with copies of the selected repos and an independent .planning directory.

Frequently Asked Questions about shine-new-workspace

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

FAQPage Schema
How do I set up an isolated multi-repo workspace for feature branches?

To set up an isolated multi-repo workspace, this Skill assembles specified git repositories into a single directory using worktrees or clones, alongside an independent .planning folder for orchestration. It validates inputs and generates a WORKSPACE.md manifest recording the configuration.

What is the difference between using git worktrees and clones for repository management?

For repository management, git worktrees create linked branches sharing a single .git directory to save disk space. Clones create entirely separate repository copies for full isolation. This Skill supports both strategies via the --strategy parameter.

Can I include an independent planning directory when automating multi-repo orchestration?

Yes, you can include an independent planning directory when automating multi-repo orchestration. The Skill automatically generates a dedicated .planning/ directory within each new workspace to hold isolated context for repeatable planning sessions.

How do I create repeatable DevOps planning environments across multiple projects?

You create repeatable DevOps planning environments by defining the workspace name, repository list, and branch. The Skill isolates these repositories with an independent .planning directory and produces a WORKSPACE.md manifest to ensure consistent setup.

Do I need specific arguments to configure repository isolation for SHINE sessions?

Yes, you need specific arguments to configure repository isolation. The Skill validates inputs and supports --name, --repos, --path, --strategy, and --branch parameters to properly assemble the isolated directories and generate the planning context.