isolatelisted

Use after a plan is approved and before any implementation dispatch. Creates an isolated workspace — a git worktree (preferred) or a fresh branch — scoped to the current vibe run. Prevents in-progress work from mixing with the user's other work, makes rollback cheap, and gives exec-dispatch a clean slate to operate in.
rizukirr/vibekit · ★ 20 · Code & Development · score 80

Install: claude install-skill rizukirr/vibekit

# isolate ## Overview Create a workspace that is dedicated to one vibe run, named after the run, branched from the user's current base, and guaranteed clean at creation. All implementation commits land in this workspace. Rollback = delete the worktree / branch. Two modes: **worktree** (default, preferred) and **branch** (fallback when worktrees are unavailable or the user prefers it). ## When to invoke - After `plan-write` has produced and committed a plan and the user has chosen an execution mode. - Before the first `exec-dispatch` task. - Only once per vibe run. Subsequent tasks in the same run reuse the same workspace. Do not invoke: - On read-only / exploratory work. - On runs the user explicitly scoped to "edit in place". - If an isolated workspace for this run already exists — reuse it. ## Naming convention Derive from the vibe run or the spec: - Worktree path: `<repo>/.vibe-worktrees/<run-id>/` where `<run-id>` is `YYYY-MM-DD-<slug>` taken from the spec filename. - Branch name: `vibe/<slug>` where `<slug>` is the spec's filename slug. Examples for a spec at `docs/specs/2026-04-21-kebab-design.md`: - Worktree path: `.vibe-worktrees/2026-04-21-kebab/` - Branch name: `vibe/kebab` Override: if the user has configured a different naming scheme (in project memory or CLAUDE.md), follow theirs. ## Preconditions (check before creating anything) - [ ] The current repo is a git repo (`.git/` exists). - [ ] The working tree is clean OR the user has explicitly authoriz