git-worktree

git-worktree is a skill for Claude Code, Codex from divingsbysangam/salesforce-compound-engineering-plugin. It costs 36 tokens per session (649 once invoked), scanned A, original, MIT.

A guide and command reference for Git worktrees, which let you check out multiple branches in separate folders while sharing one Git history.

In plain words
What is it for?
Use it to create, list, remove, or clean up isolated folders for Salesforce feature branches and hotfixes.
Why use it?
It lets developers work on a hotfix and another Salesforce change at the same time without stashing unfinished work or disturbing the current folder.

Skill for Claude CodeCodex

Part of the sf-compound-engineering plugin — 54 skills, 1 agent, 1 hook, 2 MCP servers shipped together

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/divingsbysangam/salesforce-compound-engineering-plugin/git-worktree
Any agent
npx skills add divingsbysangam/salesforce-compound-engineering-plugin --skill git-worktree
Clone the repo
git clone --depth 1 https://github.com/divingsbysangam/salesforce-compound-engineering-plugin

Made for: Claude Code, Codex.

Or install sf-compound-engineering, the plugin that ships this one along with the rest of its 54 skills, 1 agent, 1 hook, 2 MCP servers.

Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 649 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.00036 $0.00649
Opus 5 $0.00018 $0.00324
Sonnet 5 $0.00007 $0.00130
Haiku 4.5 $0.00004 $0.00065

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

Security

Grade A, and why

git-worktree 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.

skills/git-worktree/SKILL.md · 89 lines

How it starts

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

Git Worktree Skill

Manage isolated development branches using git worktrees for parallel Salesforce development.

What Are Worktrees?

Git worktrees let you have multiple branches checked out simultaneously in separate directories. Each worktree has its own working directory but shares the same .git history.

Why for Salesforce? Work on a hotfix while a feature branch has uncommitted changes, without stashing or losing context.

Quick Commands

Create a Worktree

# Create worktree for a new branch
git worktree add ../sf-feature-branch -b feature/my-feature

# Create worktree from existing branch
git worktree add ../sf-hotfix hotfix/urgent-fix

List Worktrees

git worktree list

Remove a Worktree

# After merging/completing work
git worktree remove ../sf-feature-branch

# Force remove (if changes exist)
git worktree remove --force ../sf-feature-branch

Prune Stale Worktrees

git worktree prune

Salesforce-Specific Considerations

Auth Files

When creating a new worktree, Salesforce auth files are NOT shared. You may need to:

# Copy sfdx-project.json (usually tracked in git, so it's there)
# Re-authenticate if needed
sf org login web --alias myOrg

# Or copy auth from main worktree
sf org display --target-org myOrg --verbose
# Copy the instance URL and access token

.sfdx Directory

The .sfdx/ directory contains local org authentication. Options:

  1. Symlink (recommended): ln -s /path/to/main/.sfdx .sfdx
  2. Re-auth: Run sf org login web in the new worktree
  3. Copy: cp -r /path/to/main/.sfdx .sfdx

.env Files

If using .env for configuration:

cp /path/to/main/.env .env

Workflow Pattern

main worktree (main branch)
├── feature worktree (feature/new-lwc)  ← Active development
├── hotfix worktree (hotfix/prod-fix)   ← Urgent fix
└── review worktree (review/pr-123)     ← Code review

Best Practices

  1. Name worktree directories clearly: ../sf-{purpose}-{branch}
  2. Clean up after merging: Always remove completed worktrees
  3. Don't deploy from worktrees: Deploy only from the main worktree
  4. Share auth carefully: Symlink .sfdx to avoid re-authenticating

Read the full file on GitHub · 89 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 · 89 lines · 36 tokens per session scan A 45b064cf5967

Subscribe to this mod's changes

git-worktree is a skill published in the GitHub repository divingsbysangam/salesforce-compound-engineering-plugin (10 stars, last pushed 6d ago), licensed MIT. It adds 36 tokens to every session and 649 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens