isolate
SolidUse 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.
Install
Quality Score: 81/100
Skill Content
Details
- Author
- rizukirr
- Repository
- rizukirr/vibekit
- Created
- 4 months ago
- Last Updated
- yesterday
- Language
- JavaScript
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
working-in-isolation
Use when you're about to start changing files in a repository — code, docs, config, or content, whether a feature, bugfix, refactor, or docs/config update — to establish an isolated workspace so your work doesn't collide with existing or in-progress work.
git-worktrees
Set up an isolated workspace for feature work so the current branch and working tree stay untouched — detecting existing isolation first, preferring the platform's native worktree tooling, and falling back to git worktrees only when nothing native exists. Use before starting feature work that needs isolation, or before executing an implementation plan.
worktree-isolation
Isolate non-trivial work in a sibling git worktree using `basicly worktree`, covering sibling placement on a harness branch, dependency + git-hook provisioning, and safe cleanup. Use when starting a unit of work that should not touch the main checkout, when parallel tracks would collide, or when deciding whether a change needs its own worktree.