worktree-isolation

Git worktrees can leak changes between branches if your working directory resets during operations. This Skill enforces mandatory verification of your current worktree before each git command, uses absolute paths or chained commands to preserve context, and stops write operations if the worktree context doesn't match your intent.

Chain commands to preserve context (cd /path/to/worktree && git ...), use absolute paths with git -C, and always verify your current directory and branch before writes. This Skill provides verification protocols and patterns to keep changes isolated and prevent accidental modifications to the wrong branch.

Yes. Git worktrees create isolated workspaces by design, but working directory resets can cause changes to bleed into main. This Skill applies pre-operation verification blocks, explicit worktree-context propagation, and command chaining patterns to guarantee isolation and protect your main branch.

Working directory context can reset between tool invocations, causing subsequent git operations to run in unintended worktrees. This Skill prevents that by requiring verification before writes, using absolute paths, and enforcing explicit context handling so all changes stay contained in the designated worktree.

Create separate worktrees with git worktree add, then use this Skill's patterns: announce usage, verify your current worktree before operations, chain commands to preserve context, and apply absolute paths. This ensures each worktree remains isolated and changes don't cross branches during collaborative or feature-parallel workflows.

Print your current directory, git root, and branch name before any write operation. Stop and re-check context if the worktree path or branch doesn't match your intent. This Skill builds verification into every workflow to catch misalignment early and prevent accidental commits to the wrong branch.