using-git-worktrees

Create and manage isolated git worktrees with session registry tracking.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/vTRKA/supervibe --skill using-git-worktrees-vtrka
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-git-worktrees
Source: https://github.com/vTRKA/supervibe/tree/main/skills/using-git-worktrees
Command: npx skills add https://github.com/vTRKA/supervibe --skill using-git-worktrees-vtrka

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prevent AI coding sessions from polluting the main workspace when starting feature work or executing plans that require isolated, repeatable state.

Core Features & Use Cases

  • Creates isolated worktrees for autonomous sessions or plan execution when the current workspace is clean or has been validated as safe to proceed.
  • Registers and tracks session ownership via an active worktree session registry, including heartbeat/status and cleanup policy fields.
  • Performs evidence-based verification and safe cleanup by requiring explicit verification steps (e.g., worktree list checks) and cleanup only after merge/PR completion.

Quick Start

In the AI chat, tell the agent to create an isolated git worktree for your next feature session and register it in the Supervibe worktree session registry, then switch context to the new path only after verifying the current workspace state.

Frequently Asked Questions about using-git-worktrees

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I isolate feature work from my main git workspace?

Isolating feature work from your main git workspace involves creating an isolated git worktree for autonomous sessions or plan execution. This prevents development sessions from polluting the main workspace by keeping state separate and repeatable.

What is a git worktree used for in AI coding sessions?

Using a git worktree in AI coding sessions isolates feature work or plan execution, preventing state contamination in the main workspace. It enables durable session tracking and repeatable development environments without affecting the primary branch.

How do I manage git worktree cleanup after a pull request is merged?

Managing git worktree cleanup after a pull request is merged requires tracking status via an active worktree session registry, enforcing safe cleanup only after explicit verification steps confirm merge or PR completion, ensuring no active work is lost.

Can I run parallel development sessions using git worktrees?

Running parallel development sessions using git worktrees supports parallel work isolation scenarios. Each worktree is registered and tracked with heartbeat and status fields to maintain session ownership and durability.

Do I need a clean main workspace before creating a git worktree?

Needing a clean main workspace before creating a git worktree is required, or one validated as safe to proceed. The process performs required git pre-checks and emits verification commands to ensure the current workspace state is safe before switching context.