Worktree Workspace

OrganizationPopular

udecode

worktree-workspace

Open every git worktree of a project in one VS Code window, each folder labeled by its agent session's title. Use for /worktree-workspace, reviewing worktrees in VS Code, or seeing which worktree holds which task.

Overview

Publisher	udecode
Repository	`dotai`
Skill name	`worktree-workspace`
Stars	1.2K
Forks	82
Bundled files	2
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
2 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by udecode on GitHub. Read the source before you install it.

Installation

Install the Worktree Workspace AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/udecode/dotai/tree/main/skills/worktree-workspace
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/udecode/dotai.git /tmp/dotai
mkdir -p .claude/skills
cp -r /tmp/dotai/skills/worktree-workspace .claude/skills/worktree-workspace

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Worktree Workspace in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Worktree Workspace on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Worktree Workspace is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Worktree workspace

Run node <this skill>/scripts/workspace.mjs --repo <checkout> --open from any folder. It writes <checkout parent>/<repo>-worktrees.code-workspace and opens it in VS Code.

The script labels folders and never moves them, because the app tracks a session by its working folder, and a title changes at every stage.

The main checkout comes first, labeled <repo> · <branch>.
A worktree a session works in shows that session's latest title, with (archived) when it is archived.
A worktree with no session of its own, such as one a session made from inside another folder, shows its folder name and last commit subject.
A label two folders share gets · <folder> appended.
The script lists only worktrees under <checkout>/.claude/worktrees. --all adds the rest, such as scratch proof worktrees.

Titles come from --sessions <file>, a JSON array with each session's cwd and title (Claude Code desktop's list_sessions output works), or else from the Claude desktop app's session store. The store's format is private, so the script stops with an error when it changes instead of writing unlabeled folders.

Rerun the command to refresh labels; VS Code reloads an open workspace file when it changes. Report the path and the label list it prints.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

scripts/workspace.mjs5 KB
scripts/workspace.test.mjs2 KB

Frequently asked questions

What does the Worktree Workspace AI skill do?

Why use Worktree Workspace on TypingMind?

Because you install it once and use it with any model. Worktree Workspace is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Worktree Workspace in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/udecode/dotai/tree/main/skills/worktree-workspace. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Worktree Workspace?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Worktree Workspace?

As many as you like. As long as a model supports skills, you can use Worktree Workspace with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Worktree Workspace AI skill free?

It is published on GitHub by udecode. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Solid

openclaw

OrganizationPopular

Write, port, review, or test Solid 2 UI in OpenClaw (Control UI, plugin views, Canvas hosts), including state ownership, Lit interop during the migration, native overlays, testing, performance, and…

Auto Qa

Run OpenClaw-wide autonomous QA and live/stress campaigns across independent subsystem lanes, with verified fixes and a resumable evidence report.

Autoreview

Structured code review when explicitly requested, preferring OpenAI/Codex before Claude.

Claw Score

Audit or refresh OpenClaw maturity scorecard docs from root taxonomy, maturity scores, and QA evidence artifacts without using maintainer discrawl data or committed inventory reports.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Worktree workspace

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now