Using Git Worktrees
Use when starting feature work that needs isolation or before executing implementation plans. Creates isolated git worktrees with safety verification.
Install
$ agentstack add skill-himmelreich-it-agent-skill-converter-using-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-himmelreich-it-agent-skill-converter-using-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
Using Git Worktrees
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 for .worktrees (preferred) or worktrees in the project root. If found, use that directory.
2. Check Guidelines
Check CLAUDE.md or other project guidelines for worktree preferences. If specified, use it.
3. Ask User
If no directory is found and no preference is specified, ask the user: "No worktree directory found. Where should I create worktrees?
.worktrees/(project-local, hidden)~/.config/junie/worktrees//(global location)
Which would you prefer?"
Safety Verification
For Project-Local Directories
MUST verify directory is ignored before creating worktree: git check-ignore -q .worktrees
If NOT ignored:
- Add the directory to
.gitignore. - Commit the change with the Junie co-authored trailer.
- Proceed with worktree creation.
Why critical: Prevents accidentally committing worktree contents to the repository.
Creation Steps
1. Create Worktree
- Determine the branch name.
- Create the worktree:
git worktree add -b - Change directory to the new worktree:
cd
2. Run Project Setup
Auto-detect and run appropriate setup (e.g., npm install, pip install -e ., uv sync).
Key Benefits
- Isolation - No accidental changes to your current branch.
- Speed - No need to stash/unstash when switching tasks.
- Parallelism - Work on multiple tasks at once in different worktrees.
Remember
- Always check
.gitignorefirst. - Follow project setup conventions in the new worktree.
- Inform the user of the new worktree path.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: himmelreich-it
- Source: himmelreich-it/agent-skill-converter
- License: Apache-2.0
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.