Skip to content
Skills Library
Programming · Automation

worktree

/worktree

Isolate parallel work in a git worktree of the current repository (worktree tool: status / new / merge / remove). Use when another live session is dirty in the same directory (list_agents), when two agents would fight over index.lock, or when starting a parallel task checkout.

Repository
agentica ↗
Licence
Apache-2.0
Last repository change
26.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Isolate parallel work in a git worktree of the current repository (worktree tool: status / new / merge / remove). Use when another live session is dirty in the same directory (list_agents), when two agents would fight over index.lock, or when starting a parallel task checkout.

Original author description

Isolate parallel work in a git worktree of the current repository (worktree tool: status / new / merge / remove). Use when another live session is dirty in the same directory (list_agents), when two agents would fight over index.lock, or when starting a parallel task checkout.

How it works

  1. When
  2. How
Original SKILL.md headings · 49 lines, 335 words
SKILL.md preview
---
name: worktree
description: >-
  Isolate parallel work in a git worktree of the current repository
  (worktree tool: status / new / merge / remove). Use when another live
  session is dirty in the same directory (list_agents), when two agents would
  fight over index.lock, or when starting a parallel task checkout.
metadata:
  version: "2.1"
---

# Isolate work in a worktree

Several sessions in one checkout overwrite each other and contend for git's
index. A worktree is one directory + one branch per *task*, sharing the
repository.

This session does **not** move. `worktree(action="new")` returns a path.
Pass that path as `work_dir` on `read_file` / `write_file` / `apply_patch` /
`execute`. On `glob` / `grep`, pass it as `path`. Omit those arguments and
the call stays in this session's directory.

Do not `cd` and expect later calls to follow — each call is independent.
Do not `execute` `git worktree add`: that only makes a directory, and later
calls still use this session unless you pass `work_dir` / `path`. Use
`worktree(action="new")`.

## When

- `list_agents` shows another session in this directory (dirty files, same
  branch) and you are about to edit.
- A change should not land on the shared working tree.

Not this: a read-only `task` subagent (it does not write). A second CLI
that should start already inside a tree is `agentica --worktree <task>`.

## How

Name the *task*, not yourself. Reused while the checkout is healthy; gone
after merge. A registration that is no longer a checkout is refused — remove
it first, or pick another name. The tool does not delete leftover files to
make room.

- `worktree(action="new", name="<task>")` — create or reuse; returns the path
- `worktree(action="status")` — every worktree of this repo
- `worktree(action="merge", name="<task>")` — land on local main (conflicts
  stay in that worktree, then fast-forward on main), delete the checkout
- `worktree(action="remove", name="<task>")` — drop a `wt/*` checkout git
  will allow (dirty is refused; an unmerged branch is left in place)

`new(name="main")` is refused: `main` is the repository root, not a task.

For a chunk of work big enough for its own process, `delegate(task=...,
work_dir=<path>)` already takes the same path.

If a directory goes missing, `status` labels it `(directory gone)` or
`(not a checkout)`. Say so; do not rebuild it by destroying what sits there.
`remove` the name, then `new` if you still want it.

Versions

RepositoryScoreLicence
This page · shibing624/agentica90Apache-2.0
vanducng/skills100MIT
tony/skills100MIT
zts212653/clowder-ai100MIT
duronext/jig100MIT
guangshinhaha/shinstack100MIT
PranamRDoshi/dotclaude100MIT
kronael/tools100Unlicense
rhesis-ai/rhesis100MIT

Database snapshot: 13.11.2026 · package version 1e838d0ffd6f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100git-worktree
    Use when the user asks to work in a worktree or to isolate the agent's work from other agents in the same checkout.
  • 100using-git-worktrees
    Use when starting feature work that needs isolation from current workspace, or setting up parallel development tracks. Triggers: 'worktree', 'separate branch', 'isolate this work', 'don't mess up current work', 'work on two things at once', 'parallel workstreams', 'new branch…
  • 100remove-worktree
    Use when user wants to safely remove an autonomy worktree while preserving the branch
  • 100git-worktree-finish
    Use when the user asks to finish, land, or merge back a feature worktree created with /git-worktree.
  • 100worktree-new
    Create a task worktree with `aidrian worktree new` and run the project's bootstrap. Use when a task needs one.
  • 95dev_manage_git-worktrees
    Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification. Triggers: worktree, git worktree, isolated workspace, feature branch…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.