Git Worktrees
Using git worktrees for parallel development. Trigger when the user wants to work on multiple branches simultaneously, do parallel dev, or manage worktrees.
Install
$ agentstack add skill-christopherlouet-claude-base-git-worktrees ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-christopherlouet-claude-base-git-worktrees) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Git Worktrees (pointer)
> "The single biggest productivity unlock." — Boris Cherny, creator of Claude Code
Generic worktree mechanics (git worktree add/list/remove/prune, branch isolation, hooks sharing) are canonical at git-scm.com/docs/git-worktree. This skill scopes to Claude-Code-specific worktree integration — what isn't in the git docs.
Claude Code worktree settings (CLI 2.1.76+ / 2.1.141+)
Three settings in .claude/settings.json shape how Claude Code uses worktrees:
| Setting | Values | Purpose | |---|---|---| | worktree.sparsePaths | array of globs | Limit which files a worktree includes — speeds up monorepo operations and narrows Claude's exploration context | | worktree.bgIsolation | "auto" (default) / "none" | Background sessions/agents default to writing into .claude/worktrees/; "none" lets them edit the working copy directly | | worktree.baseRef | "fresh" / "head" | "fresh" branches new worktrees from origin/, "head" from local HEAD (inherits in-progress local commits) |
Both bgIsolation and baseRef apply to --worktree, the EnterWorktree tool, and agent-isolation worktrees.
Named-session pairing pattern
The foundation-specific workflow is 1 worktree = 1 branch = 1 named Claude session:
git worktree add ../myapp-feature-auth -b feature/auth
cd ../myapp-feature-auth && claude -n "auth"The --name/-n flag tags the session for logs and terminal identification. Combined with worktrees this lets you run 5+ Claude Code sessions in parallel without state collision — see the "Parallel Sessions" section in CLAUDE.md.
See also
/work:work-explore— dedicate an analysis worktree to read-only explorationsession-handoffskill — transfer context across worktreesparallel-agents/agent-teamsskills — orchestration on top of multi-worktree setups
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: christopherlouet
- Source: christopherlouet/claude-base
- License: MIT
- Homepage: https://christopherlouet.github.io/claude-base/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.