Agent skill

Create Worktree

Create a Proton git worktree with local submodule reuse. An agent skill from timeplus-io/proton.

Apache-2.0Auto-check passedDevelopment

Install Create Worktree

skills CLI

$ npx skills add timeplus-io/proton --skill create-worktree -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install timeplus-io/proton create-worktree --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/timeplus-io/proton.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/create-worktree .claude/skills/create-worktree && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "create-worktree" agent skill from https://github.com/timeplus-io/proton/tree/develop/.claude/skills/create-worktree into .claude/skills/create-worktree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-worktree", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/timeplus-io/proton/tree/develop/.claude/skills/create-worktree

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add timeplus-io/proton --skill create-worktree -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install timeplus-io/proton create-worktree --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/timeplus-io/proton.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/create-worktree .agents/skills/create-worktree && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "create-worktree" agent skill from https://github.com/timeplus-io/proton/tree/develop/.claude/skills/create-worktree into .agents/skills/create-worktree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-worktree", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add timeplus-io/proton --skill create-worktree -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install timeplus-io/proton create-worktree --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/timeplus-io/proton.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/create-worktree .cursor/skills/create-worktree && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "create-worktree" agent skill from https://github.com/timeplus-io/proton/tree/develop/.claude/skills/create-worktree into .cursor/skills/create-worktree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-worktree", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/timeplus-io/proton.git --path .claude/skills/create-worktree

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add timeplus-io/proton --skill create-worktree -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install timeplus-io/proton create-worktree --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/timeplus-io/proton.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/create-worktree .gemini/skills/create-worktree && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "create-worktree" agent skill from https://github.com/timeplus-io/proton/tree/develop/.claude/skills/create-worktree into .gemini/skills/create-worktree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-worktree", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install timeplus-io/proton create-worktree

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add timeplus-io/proton --skill create-worktree -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/timeplus-io/proton.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/create-worktree .github/skills/create-worktree && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "create-worktree" agent skill from https://github.com/timeplus-io/proton/tree/develop/.claude/skills/create-worktree into .github/skills/create-worktree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-worktree", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add timeplus-io/proton --skill create-worktree -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install timeplus-io/proton create-worktree --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/timeplus-io/proton.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/create-worktree .opencode/skills/create-worktree && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "create-worktree" agent skill from https://github.com/timeplus-io/proton/tree/develop/.claude/skills/create-worktree into .opencode/skills/create-worktree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-worktree", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: create-worktree
GitHub stars: 2.3k
Token cost: ~812 tokens
SKILL.md length: 328 words
Files: 2 (incl. scripts)
Skills in repo: 7
Repo updated: Sep 20, 2026
First seen: Oct 8, 2026
Licence: Apache-2.0

At a glance

Create a Proton git worktree with local submodule reuse. An agent skill from timeplus-io/proton.

Works in 7 steps: Resolve paths and validate inputs → Create the worktree (using existing… → Reuse submodule git data via hardlinks… → …
The user wants to work on a separate branch in isolation
SKILL.md covers Default policy, What it does, Usage and After the script completes, plus 2 more sections
Runs Shell scripts from its folder; calls bash and git

What it does

Create Worktree is an agent skill from timeplus-io/proton. Create a Proton git worktree with local submodule reuse. Make sure to use this skill whenever the user wants to work on a separate branch in isolation, needs a clean working copy, or mentions worktrees, even if they just say 'I want to start working on issue X in a separate directory'.

Its SKILL.md is about 810 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/create_worktree.sh`).

It sits in Development, covering Git worktrees. It works with Git and C++. The repository describes itself as: The Fastest Unified Streaming SQL Engine in a Single C++ Binary. ⚡ Millisecond latency. 100+ GB/s throughput. Continuously compute real-time context from streams, logs, metrics… The licence is Apache-2.0.

When your agent uses it

The user wants to work on a separate branch in isolation
Needs a clean working copy
Mentions worktrees
Even if they just say I want to start working on issue X in a separate directory

Example prompts

“I want to start working on issue X in a separate directory”
“/create-worktree”

Requirements

A Bash shell

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

Resolve paths and validate inputs
Create the worktree (using existing local branch, remote tracking branch, or origin/develop as base)
Reuse submodule git data via hardlinks when possible (falls back to full copy)
Fix core.worktree pointers to reference the new worktree
Materialize submodule working trees
Validate submodule state
Report the result with next steps

What it can do on your machine

Read from SKILL.md and the folder at commit 1c47e60. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
- bash
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Create Worktree loads about 812 tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 328 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~76
When it runs · the whole SKILL.md, loaded when a task matches: ~812

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from timeplus-io/proton at commit 1c47e60, republished under its Apache-2.0 licence (© timeplus-io). 328 words, ~812 tokens.

Download SKILL.mdSave it as .claude/skills/create-worktree/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: create-worktree
description: Create a Proton git worktree with local submodule reuse. Make sure to use this skill whenever the user wants to work on a separate branch in isolation, needs a clean working copy, or mentions worktrees, even if they just say 'I want to start working on issue X in a separate directory'.

Create Worktree

Default policy

Use a dedicated worktree by default for any task that writes code, creates a branch/commit, or needs isolated build/test output.

Do not pay the worktree cost for pure read-only tasks such as code search, documentation lookup, or review-only requests unless the user explicitly asks for isolation.

What it does

Creates a worktree without re-downloading the repo's submodule data. This repo has a large contrib/ tree, so submodule reuse matters for both speed and disk usage.

The script isolates three things together:

source-tree changes
submodule working trees
build/test artifacts that must stay bound to one source root

Usage

Run the bundled script:

bash

bash .claude/skills/create-worktree/scripts/create_worktree.sh <branch> [worktree-path]

branch (required): branch name (e.g. bugfix/issue-3446-session-watermark-regression)
worktree-path (optional): defaults to .worktrees/<safe-branch> under the repo root

The script will:

Resolve paths and validate inputs
Create the worktree (using existing local branch, remote tracking branch, or origin/develop as base)
Reuse submodule git data via hardlinks when possible (falls back to full copy)
Fix core.worktree pointers to reference the new worktree
Materialize submodule working trees
Validate submodule state
Report the result with next steps

After the script completes

Initialize a build directory inside the worktree:

bash

cd <worktree-path>
mkdir -p build && cd build && ../build.sh Debug

Do not replace this with direct cmake configure commands unless the user explicitly asks for that.

Do not reuse build* directories from the main checkout — CMake/Ninja build directories embed absolute source paths, so reusing them will either build the wrong tree or overwrite the original checkout's configuration.

Examples

bash

# Feature branch with default worktree path
bash .claude/skills/create-worktree/scripts/create_worktree.sh bugfix/issue-3446-session-watermark-regression

# Custom worktree path
bash .claude/skills/create-worktree/scripts/create_worktree.sh chore/worktree-skill-build-isolation ../proton-worktree-skill-build-isolation

Notes

This is local-only and should not need network access if the main repo already has submodules initialized.
Build artifacts are not shared across source roots. Reconfigure/build inside the worktree you are validating.
Prefer this skill instead of inlining raw git worktree add.
To remove a clean worktree later (run from the main checkout, not from inside the worktree):

bash

git -C /path/to/main/repo worktree remove <worktree-path>

If removal is blocked by uncommitted or untracked files, inspect or back up that work first. Only use forced cleanup when you intentionally want to discard it:

bash

git worktree remove --force <worktree-path>

Files

SKILL.md and 1 other file (scripts) in .claude/skills/create-worktree of timeplus-io/proton.

SKILL.md
scripts/create_worktree.sh

Open the folder on GitHubat commit 1c47e60

Compare with similar skills

Create Worktree next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Create Worktree compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Create Worktree this skilltimeplus-io/proton	2.3k	—	~812	Automated safety check: Pass	Apache-2.0	18 days ago
Setup Devrelytcloud/pg_ducklake	143	—	~2k	Automated safety check: Notes	MIT	1 mo ago
Finishing a Development Branchobra/superpowers	296k	5 repos	~1.9k	Automated safety check: Pass	MIT	today
Finishing A Development Branchfarm-fe/farm	5.6k	34 repos	~1.8k	Automated safety check: Pass	MIT	16 days ago
Git Worktree Cleanuplobehub/lobehub	83k	—	~2.8k	Automated safety check: Pass	Custom licence	today
Pre-Release PR Triagejamiepine/voicebox	57k	—	~3.1k	Automated safety check: Pass	MIT	yesterday

Similar skills

Setup Dev
relytcloud/pg_ducklake
Dev environment setup for build tools, PostgreSQL, submodules, and worktrees.
143 GitHub stars~2k tokensUpdated 1 mo ago
DevelopmentAuto-check: notes
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
296k GitHub starsUsed in 5 repos~1.9k tokens
DevelopmentAuto-check passed
Finishing A Development Branch
farm-fe/farm
A skill your agent uses when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for…
5.6k GitHub starsUsed in 34 repos~1.8k tokens
DevelopmentAuto-check passed
Git Worktree Cleanup
lobehub/lobehub
Audits stale Git worktrees and branches with a bundled script, classifies each one, and deletes only after you approve the exact candidates.
83k GitHub stars~2.8k tokensUpdated today
DevelopmentAuto-check passed
Pre-Release PR Triage
jamiepine/voicebox
Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.
57k GitHub stars~3.1k tokensUpdated yesterday
DevelopmentAuto-check passed
Qt C++ Code Review
x-tools-author/x-tools
Read-only review of Qt6 C++ code that combines a deterministic lint script with six parallel analysis agents and reports only high-confidence issues.
1.1k GitHub starsUsed in 2 repos~4.3k tokens
DevelopmentAuto-check passed

Questions about Create Worktree

What does Create Worktree do?

Create a Proton git worktree with local submodule reuse. An agent skill from timeplus-io/proton. Create Worktree is an agent skill from timeplus-io/proton. Create a Proton git worktree with local submodule reuse.

When should I use Create Worktree?

Create Worktree fits situations like: the user wants to work on a separate branch in isolation; needs a clean working copy; mentions worktrees; even if they just say I want to start working on issue X in a separate directory.

How do I install Create Worktree in Claude Code?

Run `npx skills add timeplus-io/proton --skill create-worktree -a claude-code`. Or copy the skill folder (.claude/skills/create-worktree in timeplus-io/proton) into .claude/skills/create-worktree in your project. Claude Code loads it when a task matches its description.

How do I install Create Worktree in Codex?

Run `npx skills add timeplus-io/proton --skill create-worktree -a codex`. Or copy the skill folder (.claude/skills/create-worktree in timeplus-io/proton) into .agents/skills/create-worktree in your project. Codex loads it when a task matches its description.

Can I use Create Worktree in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add timeplus-io/proton --skill create-worktree -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-worktree, .gemini/skills/create-worktree, .github/skills/create-worktree and .opencode/skills/create-worktree in your project.

What does Create Worktree need to run?

Going by SKILL.md and its folder, Create Worktree needs a shell for the scripts in its folder and the command-line tools its instructions call (bash and git). Our summary lists: A Bash shell.

Does Create Worktree access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Create Worktree safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Create Worktree use?

Create Worktree is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Create Worktree use?

About 812 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Create Worktree?

Skills that share tags, products or a category with Create Worktree: Setup Dev (relytcloud/pg_ducklake, 143 stars), Finishing a Development Branch (obra/superpowers, 296k stars), Finishing A Development Branch (farm-fe/farm, 5.6k stars) and Git Worktree Cleanup (lobehub/lobehub, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Create Worktree?

timeplus-io (a GitHub organization) maintains it in timeplus-io/proton, which has 2,265 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on September 20, 2026.

Source: timeplus-io/proton on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Create Worktree

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Create Worktree

Default policy

What it does

Usage

After the script completes

Examples

Notes

Files

Compare with similar skills

Similar skills

More from timeplus-io/proton

Related

Questions about Create Worktree