using-git-worktrees

A guide to Git worktrees, which are separate working folders connected to one Git repository and branch.

In plain words
What is it for?
Setting up an isolated folder for planned development, selecting its location, and checking that the setup is safe.
Why use it?
It keeps feature work isolated so an agent can work without changing the current workspace or switching its branch.

Skill for Claude CodeCodex

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/zhanglongxiao111/indesign-cli/using-git-worktrees
Any agent
npx skills add zhanglongxiao111/indesign-cli --skill using-git-worktrees
Clone the repo
git clone --depth 1 https://github.com/zhanglongxiao111/indesign-cli

Made for: Claude Code, Codex.

Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,657 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.

ModelPer sessionOnce invoked
Fable 5 $0.00045 $0.01657
Opus 5 $0.00023 $0.00829
Sonnet 5 $0.00009 $0.00331
Haiku 4.5 $0.00005 $0.00166

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

Security

Grade A, and why

using-git-worktrees 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 3d 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.

.codex/skills/using-git-worktrees/SKILL.md · 251 lines

How it starts

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

Using Git Worktrees

Overview

Git worktrees create isolated workspaces sharing the same repository, allowing work on multiple branches simultaneously without switching.

Core principle: Systematic directory selection + safety verification = reliable isolation.

Announce at start: "I'm using the using-git-worktrees skill to set up an isolated workspace."

Directory Selection Process

Follow this priority order:

1. Check Existing Directories

# Check in priority order
ls -d .worktrees 2>/dev/null     # Preferred (hidden)
ls -d worktrees 2>/dev/null      # Alternative

If found: Use that directory. If both exist, .worktrees wins.

2. Check AGENTS.md

grep -i "worktree" AGENTS.md 2>/dev/null

If preference specified: Use it without asking.

3. Check CLAUDE.md (Backward Compatibility Only)

grep -i "worktree" CLAUDE.md 2>/dev/null

Use only if AGENTS.md is absent or has no worktree convention.

4. Ask User

If no directory exists and no AGENTS.md / CLAUDE.md preference:

No worktree directory found. Where should I create worktrees?

1. .worktrees/ (project-local, hidden)
2. ~/.config/superpowers/worktrees/<project-name>/ (global location)

Which would you prefer?

Safety Verification

AGENTS.md Overrides Generic Defaults

If AGENTS.md defines a worktree convention, follow it exactly.

Examples:

  • sibling directory naming such as SA-AIAPP-<task-slug>
  • branch naming such as codex/<task-slug>
  • repository-specific setup or baseline verification commands

Do not override a repository-local convention with this skill's generic .worktrees/ preference.

For Project-Local Directories (.worktrees or worktrees)

MUST verify directory is ignored before creating worktree:

# Check if directory is ignored (respects local, global, and system gitignore)
git check-ignore -q .worktrees 2>/dev/null || git check-ignore -q worktrees 2>/dev/null

If NOT ignored:

Read the full file on GitHub · 251 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.

  1. 3d ago First seen · 251 lines · 45 tokens per session scan A fa7c1f438e88

Subscribe to this mod's changes

using-git-worktrees is a skill published in the GitHub repository zhanglongxiao111/indesign-cli (42 stars, last pushed 14d ago), licensed MIT. It adds 45 tokens to every session and 1,657 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

indd

Run InDesign ExtendScript (.jsx) on macOS by writing a script to a local file and executing it in Adobe InDesign via AppleScript (osascript). Use when the user wants to automate Adobe InDesign — create/modify documents, place images, build tables, export PDF/PNG/JPG/EPS, read fonts/styles/colors, convert IDML, or…

mindboard/indesign-extendscript-plugins · 87 tokens

idml

Unpack and repack Adobe InDesign IDML files as editable XML, then edit the XML directly — no InDesign required. Use when the user wants to inspect, diff, or programmatically edit an .idml (stories/text, styles, colors, spreads, links) and produce a valid .idml back, or to convert between an .idml and its extracted…

mindboard/indesign-extendscript-plugins · 81 tokens

develop-premiere-pro-mcp

Develop, debug, test, review, document, and release the premiere-pro-mcp repository. Use when changing MCP tools, schemas, server registration, CEP or UXP bridges, generated ExtendScript, authority profiles, packaging, release metadata, or compatibility claims in this repo.

leancoderkavy/premiere-pro-mcp · 62 tokens

edit-premiere-project

Inspect, edit, verify, save, and export an open Adobe Premiere Pro project through the premiere-pro MCP server. Use for rough cuts, timeline assembly or cleanup, clip and track changes, transitions and effects, dialogue or audio adjustments, captions, project organization, frame inspection, and delivery exports.

leancoderkavy/premiere-pro-mcp · 64 tokens

style-guide

Help a motion designer capture their house style — palette, type, motion and layout — into the house-style.md file that sits next to their After Effects project and shapes everything built afterwards. Load when the user asks to create, edit or review their style guide, when they say work does not look like theirs, or…

Engine-Room-Games/after-effects-mcp · 74 tokens

after-effects

How to drive Adobe After Effects well through the AE MCP tools — orienting in a project, building and animating layers, keyframes and easing, expressions, effects, text and shapes, and the gotchas that silently produce wrong output. Load whenever a task involves After Effects, motion graphics, comps, layers, or…

Engine-Room-Games/after-effects-mcp · 70 tokens