Worktree Isolation
Use when feature work, plan execution, or parallel Agents need isolation from the current checkout and changes must remain recoverable.
Install
npx skills add sandbaseai/workbuddy-skill --skill worktree-isolationgit clone --depth 1 https://github.com/sandbaseai/workbuddy-skill.git /tmp/workbuddy-skill
mkdir -p ~/.claude/skills
cp -r /tmp/workbuddy-skill/skills/worktree-isolation ~/.claude/skills/worktree-isolationPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Git Worktree Isolation ## Purpose Use a linked Git worktree when edits, experiments, plan execution, or parallel Agent work must be separated from the current checkout. Isolation is a safety boundary, not a substitute for authorization: record the allowed branch, files, remotes, and external effects before creating or reusing a workspace. ## Step 0: detect current state Before creating anything, inspect the checkout without mutating it: ```bash git rev-parse --show-toplevel git rev-parse --git-dir git rev-parse --git-common-dir git rev-parse --show-superproject-working-tree 2>/dev/null git branch --show-current git status --short --branch git worktree list --porcelain ``` Treat `git-dir != git-common-dir` as a linked worktree only after confirming the checkout is not a submodule. If already isolated, reuse it when its branch, path, cleanliness, and authority match the task; do not nest another worktree by habit. A detached HEAD requires an explicit branch or externally managed handoff before integration. ## Step 1: choose and verify a workspace Honor an explicit WorkBuddy or user workspace preference. Otherwise prefer an existing project-local `.worktrees/`, then `worktrees/`, and finally a sibling path that does not overlap another checkout. Before using a project-local directory, verify it is ignored: ```bash git check-ignore -q .worktrees || git check-ignore -q worktrees ```
Details
- Skill name
worktree-isolation- Repository
- sandbaseai/workbuddy-skill
- Path
skills/worktree-isolation/SKILL.md- License
- MIT
- Repo updated
- 8 September 2026
FAQ
What does the Worktree Isolation skill do?
Use when feature work, plan execution, or parallel Agents need isolation from the current checkout and changes must remain recoverable.
How do I install the Worktree Isolation skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add sandbaseai/workbuddy-skill --skill worktree-isolation. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Worktree Isolation popular?
It lives in sandbaseai/workbuddy-skill, which has 9 GitHub stars and 3 forks.
Related skills
Access Control Security Best Practices
9sandbaseai/workbuddy-skill
Design, review, implement, and verify least-privilege access controls across users, services, tenants, resources, and administrative workflows.
Accessibility Review
9sandbaseai/workbuddy-skill
Use when reviewing a web interface or interaction for semantic, keyboard, focus, screen-reader, ARIA, and contrast accessibility risks.
Acquire Codebase Knowledge
9sandbaseai/workbuddy-skill
Use when the user asks to map, document, or onboard into an existing codebase and needs evidence-backed architecture, structure, conventions, integrations, testing, and concerns documentation.
Analyze Branch
5tilmon-engineering/claude-skills
Use when analyzing another branch's iteration journals to extract findings, decisions, and insights from divergent work
Secret Scanning
9sandbaseai/workbuddy-skill
Use when configuring GitHub secret scanning, push protection, custom patterns, alert triage, or pre-commit secret checks.
Branch Status
5tilmon-engineering/claude-skills
Use when user wants detailed status report for single autonomy branch including iteration timeline and metrics progression
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.