Ring:Creating Worktrees logo

Ring:Creating Worktrees

Organization
LerianStudio
ring:creating-worktrees

Creating an isolated git worktree for parallel branch work: selects the directory by priority order, verifies/adds .gitignore safety, auto-installs the detected toolchain's dependencies, runs a baseline test, and reports readiness. Use before a feature that needs isolation from the main workspace or before executing an implementation plan. Skip for a quick fix on the current branch or when already in the feature's worktree.

Overview

PublisherLerianStudio
Repositoryring
Skill namering:creating-worktrees
Stars
215
Forks
28
Bundled files
Instructions only
LicenseApache-2.0
Links
  • 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.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by LerianStudio on GitHub. Read the source before you install it.

Installation

Install the Ring:Creating Worktrees AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

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.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. 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.
2

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/LerianStudio/ring.git /tmp/ring
mkdir -p .claude/skills
cp -r /tmp/ring/default/skills/creating-worktrees .claude/skills/lerianstudio-ring-creating-worktrees
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ring:Creating Worktrees 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 Ring:Creating Worktrees 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 Ring:Creating Worktrees 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.

Using Git Worktrees

When to use

  • Starting feature that needs isolation from main workspace
  • Before executing implementation plan
  • Working on multiple features simultaneously

Skip when

  • Quick fix in current branch → stay in place
  • Already in isolated worktree for this feature → continue
  • Repository doesn't use worktrees → use standard branch workflow

Sequence

Runs before: ring:writing-plans

Git worktrees create isolated workspaces sharing the same repository for parallel branch work.

Announce at start: "Using ring:creating-worktrees skill to set up isolated workspace."

Directory Selection (priority order)

  1. Existing .worktrees/ or worktrees/ directory
  2. CLAUDE.md preference (grep -i "worktree.*director" CLAUDE.md)
  3. Ask user: .worktrees/ (project-local, hidden) OR ~/.config/ring/worktrees/<project>/ (global)
bash
ls -d .worktrees worktrees 2>/dev/null

Safety Verification

Project-local directories only: Verify .gitignore before creating:

bash
grep -q "^\.worktrees/$\|^worktrees/$" .gitignore

Not in .gitignore → add it → commit → proceed. (Prevents accidentally tracking worktree contents.)

Global directory (~/.config/ring/worktrees): No verification needed.

Creation Steps

bash
# 1. Detect project name
project=$(basename "$(git rev-parse --show-toplevel)")

# 2. Create worktree
git worktree add "$path" -b "$BRANCH_NAME" && cd "$path"

# 3. Auto-detect and run setup
[ -f package.json ] && npm install
[ -f Cargo.toml ] && cargo build
[ -f requirements.txt ] && pip install -r requirements.txt
[ -f pyproject.toml ] && poetry install
[ -f go.mod ] && go mod download

# 4. Verify clean baseline
npm test / cargo test / pytest / go test ./...

If tests fail: Report failures, ask whether to proceed.
If tests pass: Report: Worktree ready at <path> | Tests passing (<N> tests) | Ready to implement <feature>

Quick Reference

SituationAction
.worktrees/ existsUse it (verify .gitignore)
Both .worktrees/ and worktrees/ existUse .worktrees/
Neither existsCheck CLAUDE.md → ask user
Directory not in .gitignoreAdd immediately + commit
Tests fail during baselineReport failures + ask

Non-Negotiables

  • Project-local directories MUST be in .gitignore before creation
  • Baseline test verification REQUIRED before proceeding with work
  • Directory selection MUST follow priority order
  • Dependency installation MUST run (auto-detect from project files)

Integration

Pairs with finishing-a-development-branch for cleanup and ring:running-dev-cycle for work.

Frequently asked questions

What does the Ring:Creating Worktrees AI skill do?

Creating an isolated git worktree for parallel branch work: selects the directory by priority order, verifies/adds .gitignore safety, auto-installs the detected toolchain's dependencies, runs a baseline test, and reports readiness. Use before a feature that needs isolation from the main workspace or before executing an implementation plan. Skip for a quick fix on the current branch or when already in the feature's worktree.

Why use Ring:Creating Worktrees on TypingMind?

Because you install it once and use it with any model. Ring:Creating Worktrees 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 Ring:Creating Worktrees in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/LerianStudio/ring/tree/main/default/skills/creating-worktrees. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Ring:Creating Worktrees?

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 Ring:Creating Worktrees?

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

Is the Ring:Creating Worktrees AI skill free?

Yes. It is published on GitHub by LerianStudio under the Apache-2.0 license. 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

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇