New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Conducty Worktrees

by robertbarclayy in robertbarclayy/conducty

Git worktree lifecycle for parallel prompt execution. An agent skill from robertbarclayy/conducty.

MITAuto-check passedDevelopment

Install Conducty Worktrees

skills CLI
$ npx skills add robertbarclayy/conducty --skill conducty-worktrees -a claude-code

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

GitHub CLI
$ gh skill install robertbarclayy/conducty conducty-worktrees --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/robertbarclayy/conducty.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/conducty-worktrees .claude/skills/conducty-worktrees && 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/

Facts

Skill name
conducty-worktrees
GitHub stars
176
Token cost
~934 tokens
SKILL.md length
433 words
Files
1
Skills in repo
20
Repo updated
First seen
Licence
MIT

At a glance

Git worktree lifecycle for parallel prompt execution. An agent skill from robertbarclayy/conducty.

  • Works in 6 steps: Wait for Tracer → Create Worktrees → Verify Baselines → …
  • A parallelization group has 2+ prompts targeting the same repo
  • SKILL.md covers When to Use, Tracer Worktree Strategy, Workflow and Guidelines
  • Calls git

What it does

Conducty Worktrees is an agent skill from robertbarclayy/conducty. Git worktree lifecycle for parallel prompt execution. Creates isolated worktrees per prompt, verifies baselines, merges after checkpoint, cleans up. Use when a parallelization group has 2+ prompts targeting the same repo, or the user says "worktree", "isolate", "parallel branches".

Its SKILL.md is about 930 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Git worktrees. It works with Git. The repository describes itself as: Stop context-switching. Start batch-planning. Conducty replaces the fragmented cycle of plan → prompt → wait → get distracted → review → fix → repeat with advanced batch planning. The licence is MIT.

When your agent uses it

  • A parallelization group has 2+ prompts targeting the same repo
  • The user says worktree
  • Parallel branches

Example prompts

  • “worktree”
  • “isolate”
  • “parallel branches”
  • “/conducty-worktrees”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Wait for Tracer
  2. Create Worktrees
  3. Verify Baselines
  4. Execute
  5. Merge After Checkpoint
  6. Clean Up

What it can do on your machine

Read from SKILL.md and the folder at commit 64aefd5. 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

    Shell commands in SKILL.md call:

    • 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

Conducty Worktrees loads about 934 tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 433 words of instructions outside code blocks.

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

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from robertbarclayy/conducty at commit 64aefd5, republished under its MIT licence (© robertbarclayy). 433 words, ~934 tokens.

Download SKILL.mdSave it as .claude/skills/conducty-worktrees/SKILL.md (or your agent's skills folder).
name
conducty-worktrees
description
Git worktree lifecycle for parallel prompt execution. Creates isolated worktrees per prompt, verifies baselines, merges after checkpoint, cleans up. Use when a parallelization group has 2+ prompts targeting the same repo, or the user says "worktree", "isolate", "parallel branches".
aliases
conducty-worktrees, worktrees
tags
conducty/skill, conducty/execute, conducty/git

Conducty Worktrees — Parallel Isolation

Use git worktrees (Bash) to isolate parallel prompts that target the same repository, preventing conflicts during concurrent execution.

When to Use

Use worktrees when a parallelization group has two or more prompts targeting the same repository. If all prompts in a group target different repos, worktrees are unnecessary.

[!tip] Claude Code shortcut When dispatching a subagent via the Task tool, pass isolation: "worktree" to let the harness create and clean up a temporary worktree automatically. Use this skill when you need explicit, named worktrees that survive across multiple subagent dispatches in the same group.

Tracer Worktree Strategy

The tracer prompt (marked ★ TRACER) runs on the main branch, not in a worktree. It validates plan assumptions against the real repo state. Only after the tracer passes do you create worktrees for the remaining prompts.

This ensures the tracer tests reality, not an isolated copy.

Workflow

Step 1: Wait for Tracer

The tracer prompt executes first on the main branch (via [[conducty-execute]]). If it passes, proceed. If it fails, the plan needs revision — don't create worktrees for a flawed plan.

Step 2: Create Worktrees

For each remaining prompt that targets the same repo:

bash
cd /path/to/project
git worktree add ../conducty-wt-P{N} -b conducty/P{N}

This creates:

  • A sibling directory conducty-wt-P{N} with a full working copy
  • A branch conducty/P{N} tracking the current HEAD (which now includes the tracer's commits)

Update each prompt's Directory field in the plan to point to the worktree path (Edit tool).

Step 3: Verify Baselines

For each worktree, run the project's test suite or build command (Bash):

bash
cd ../conducty-wt-P{N}
# run project-specific test/build command

If the baseline fails, the worktree inherits a broken state — flag this before execution begins. A broken baseline wastes the entire prompt.

Show full SKILL.md (160 more words)Show less
Step 4: Execute

Prompts execute in parallel, each in its own worktree directory. No action needed from this skill during execution.

Step 5: Merge After Checkpoint

After [[conducty-checkpoint]] passes for the group, merge each worktree branch back:

bash
cd /path/to/project
git merge conducty/P{N} --no-ff -m "conducty: merge P{N} — {short description}"

Merge in order of least-dependent to most-dependent when possible.

If there are merge conflicts:

  1. Report the conflict to the user
  2. Suggest resolving in dependency order
  3. After resolution, re-run the verification command from the affected prompt
Step 6: Clean Up

After all branches are merged (or blocked prompts noted):

bash
cd /path/to/project
git worktree remove ../conducty-wt-P{N}
git branch -d conducty/P{N}

Guidelines

  • Only create worktrees for prompts sharing a repo within the same group
  • Use --no-ff merges so each prompt's work is visible as a distinct merge commit
  • Blocked prompts: clean up worktree but keep the branch for reference
  • Worktree paths should be siblings of the project directory, not nested inside
  • Always verify baseline before execution — a broken baseline wastes a prompt slot
  • This skill pairs with [[conducty-checkpoint]] — always run checkpoint before merging

© robertbarclayy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/conducty-worktrees of robertbarclayy/conducty.

Open the folder on GitHubat commit 64aefd5

Compare with similar skills

Conducty Worktrees 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.

Conducty Worktrees compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Conducty Worktrees this skillrobertbarclayy/conducty176—~934Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Finishing A Development Branchfarm-fe/farm5.6k34 repos~1.8kAutomated safety check: PassMIT
Git Worktree Cleanuplobehub/lobehub83k—~2.8kAutomated safety check: PassCustom licence
Pre-Release PR Triagejamiepine/voicebox57k—~3.1kAutomated safety check: PassMIT
Ccmanager Configkbwo/ccmanager1.3k—~1.5kAutomated safety check: PassMIT

Similar skills

  • 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.

    297k 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 2 days ago
    DevelopmentAuto-check passed

  • Ccmanager Config

    kbwo/ccmanager

    Set up, review, or repair a CCManager config — .ccmanager.json at a git repository root, or the global ~/.config/ccmanager/config.json.

    1.3k GitHub stars~1.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Cap Feature Building Workflow

    CapSoftware/Cap

    Builds a Cap feature in an isolated Git worktree with disposable dev resources, verification, a recorded demo and a neutral pull request, started with /building.

    23k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check: warnings

More from robertbarclayy/conducty

All 20 skills in this repo

  • Conducty Checkpoint

    robertbarclayy/conducty

    Quality gate between parallelization groups. An agent skill from robertbarclayy/conducty.

    176 GitHub stars~1.5k tokensUpdated 3 mo ago
    Auto-check passed

  • Conducty Code Review

    robertbarclayy/conducty

    Standalone post-implementation code review across a whole branch or PR.

    176 GitHub stars~2k tokensUpdated 3 mo ago
    Auto-check passed

  • Conducty Context

    robertbarclayy/conducty

    Ingest a project directory into the Obsidian vault as a linked context sub-graph — Architecture, Conventions, Invariants, Hotspots, Tests, Glossary, plus per-bounded-context module notes.

    176 GitHub stars~3.7k tokensUpdated 3 mo ago
    Auto-check passed

  • Conducty Debug

    robertbarclayy/conducty

    Leverage-point analysis for failed prompts. An agent skill from robertbarclayy/conducty.

    176 GitHub stars~1.9k tokensUpdated 3 mo ago
    Auto-check passed

  • Conducty Execute

    robertbarclayy/conducty

    Dispatches Claude Code Task subagents to run prompts from a vault plan note.

    176 GitHub stars~2.5k tokensUpdated 3 mo ago
    Auto-check passed

  • Conducty Improve

    robertbarclayy/conducty

    End-of-plan improvement kata. An agent skill from robertbarclayy/conducty.

    176 GitHub stars~1.5k tokensUpdated 3 mo ago
    Auto-check passed

Works with

Categories

Questions about Conducty Worktrees

What does Conducty Worktrees do?

Git worktree lifecycle for parallel prompt execution. An agent skill from robertbarclayy/conducty. Conducty Worktrees is an agent skill from robertbarclayy/conducty. Git worktree lifecycle for parallel prompt execution.

When should I use Conducty Worktrees?

Conducty Worktrees fits situations like: A parallelization group has 2+ prompts targeting the same repo; the user says worktree; parallel branches.

How do I install Conducty Worktrees in Claude Code?

Run `npx skills add robertbarclayy/conducty --skill conducty-worktrees -a claude-code`. Or copy the skill folder (skills/conducty-worktrees in robertbarclayy/conducty) into .claude/skills/conducty-worktrees in your project. Claude Code loads it when a task matches its description.

How do I install Conducty Worktrees in Codex?

Run `npx skills add robertbarclayy/conducty --skill conducty-worktrees -a codex`. Or copy the skill folder (skills/conducty-worktrees in robertbarclayy/conducty) into .agents/skills/conducty-worktrees in your project. Codex loads it when a task matches its description.

Can I use Conducty Worktrees 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 robertbarclayy/conducty --skill conducty-worktrees -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/conducty-worktrees, .gemini/skills/conducty-worktrees, .github/skills/conducty-worktrees and .opencode/skills/conducty-worktrees in your project.

What does Conducty Worktrees need to run?

Going by SKILL.md and its folder, Conducty Worktrees needs the command-line tools its instructions call (git).

Does Conducty Worktrees 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 Conducty Worktrees 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. Review the folder before installing.

What licence does Conducty Worktrees use?

Conducty Worktrees is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Conducty Worktrees use?

About 934 tokens (SKILL.md is roughly 3.7k 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 Conducty Worktrees?

Skills that share tags, products or a category with Conducty Worktrees: Finishing a Development Branch (obra/superpowers, 297k stars), Finishing A Development Branch (farm-fe/farm, 5.6k stars), Git Worktree Cleanup (lobehub/lobehub, 83k stars) and Pre-Release PR Triage (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Conducty Worktrees?

robertbarclayy (a GitHub user) maintains it in robertbarclayy/conducty, which has 176 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on June 19, 2026.

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