What is worktree-support?

A set of rules for finding files and running Git commands when a project has multiple linked working folders, called worktrees.

It helps commands discover worktrees, choose the right branch, and resolve Git, documentation, and source-file paths from the correct folder.

It prevents an agent from reading or changing files in the wrong worktree when several branches are checked out at once.

worktree-support — Skill by dean0x

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/dean0x/devflow/worktree-support

Any agent

npx skills add dean0x/devflow --skill worktree-support

Clone the repo

git clone --depth 1 https://github.com/dean0x/devflow

Made for: Claude Code, Codex.

Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 752 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00016	$0.00752
Opus 5	$0.00008	$0.00376
Sonnet 5	$0.00003	$0.00150
Haiku 4.5	$0.00002	$0.00075

Measured 2d ago against content hash 8c91c4cff2f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

worktree-support scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

src/assets/skills/worktree-support/SKILL.md · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Worktree Support

Canonical patterns for worktree-aware agents and multi-worktree discovery in commands.

Iron Law

WORKTREE_PATH IS A PREFIX, NOT A FLAG

When WORKTREE_PATH is provided, it changes how you resolve ALL paths — git commands, file reads, .devflow/docs/ paths. It's not a toggle; it's a coordinate system shift.

Agent Path Resolution

When WORKTREE_PATH is provided to an agent:

Operation	Without WORKTREE_PATH	With WORKTREE_PATH
Git commands	`git ...`	`git -C {WORKTREE_PATH} ...`
.devflow/docs/ paths	`.devflow/docs/...`	`{WORKTREE_PATH}/.devflow/docs/...`
Source files	`{file}`	`{WORKTREE_PATH}/{file}`
Default	Use cwd	Use WORKTREE_PATH as root

If WORKTREE_PATH is omitted, behavior is unchanged (use cwd). This is the common case.

Worktree Discovery Algorithm (Commands)

For commands that auto-discover worktrees (/code-review, /resolve):

Step 1: List Worktrees

Run git worktree list --porcelain

Step 2: Parse Each Entry

Extract: worktree {path}, HEAD {sha}, branch refs/heads/{name}

Step 3: Filter

Exclude:

Bare worktrees (no branch)
Detached HEAD (no named branch)
Protected branches: main, master, develop, integration, trunk, release/*, staging, production
Mid-rebase or mid-merge: check git -C {path} status for "rebase in progress" or "merging"

Step 4: Check for Work

Each worktree must have commits ahead of base branch. Skip those that are clean/up-to-date.

Step 5: Deduplicate

If two worktrees are on the same branch, use only the first worktree's path.

Step 6: Sort

Sort by last commit date (most recent first).

Step 7: Return

Return list of reviewable worktrees with path, branch, HEAD SHA.

Protected Branches (Canonical List)

main, master, develop, integration, trunk, release/*, staging, production

All components (agents, commands, skills) must use this exact list when checking for protected branches. The HUD mirrors this list in TRUNK_BRANCHES/TRUNK_BRANCH_PREFIXES/isTrunkBranch() in src/core/git.ts — update both together.

Read the full file on GitHub · 93 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 93 lines · 16 tokens per session scan A 8c91c4cff2f7

Subscribe to this mod's changes

worktree-support is a skill published in the GitHub repository dean0x/devflow (19 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 752 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Code review Git and workflow Writing and docs agent-teams ai claude-code cli developer-tools

worktree-support