adv-worktree

Manage git worktree lifecycles with Temporal state orchestration and merge-before-delete safety.

4|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Sharper-Flow/Advance --skill adv-worktree
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adv-worktree
Source: https://github.com/Sharper-Flow/Advance/tree/main/skills/adv-worktree
Command: npx skills add https://github.com/Sharper-Flow/Advance --skill adv-worktree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of context loss and environment pollution during complex AI-assisted development by providing a governed, isolated workspace for every task.

Core Features & Use Cases

  • Branch Isolation: Creates and manages git worktrees to keep experimental or risky changes separate from the main codebase.
  • Temporal Coordination: Ensures that worktree state is tracked and synchronized across sessions, preventing race conditions.
  • Safety Gates: Enforces a strict merge-before-delete protocol to prevent the accidental loss of unmerged work.
  • Use Case: When starting a large refactor or a parallel experiment, use this skill to spin up a dedicated worktree that keeps your primary branch clean and your development state persistent.

Quick Start

Use the adv-worktree skill to create a new isolated worktree for the feature branch named user-auth-refactor.

Frequently Asked Questions about adv-worktree

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

FAQPage Schema
How do I use git worktree for parallel development without losing context?

Git worktree provides isolated working directories for separate branches, ensuring state persistence and preventing environment pollution during parallel development. It keeps risky refactoring changes physically separate from your primary codebase while maintaining context across sessions.

What is the safest way to clean up a git worktree after finishing a feature branch?

The safest cleanup method is a merge-before-delete protocol that enforces merging all worktree changes back to the main branch before removal. This safety gate prevents accidental loss of unmerged experimental work during parallel development.

Do I need Temporal integration to orchestrate worktree state across sessions?

Temporal integration is required to orchestrate and synchronize worktree state across sessions. This temporal coordination prevents race conditions during parallel development by ensuring the worktree lifecycle is strictly governed and state persists reliably.

When should I use branch isolation for AI-assisted development?

Use branch isolation when starting large refactors or parallel experiments in AI-assisted development. It provides a governed, isolated workspace keeping your primary branch clean and ensuring development state persistence without polluting the main environment.

Why does my parallel development workflow suffer from race conditions and state loss?

Race conditions and state loss occur in standard worktree workflows lacking temporal coordination. Without a governed environment to synchronize worktree state across sessions, concurrent branches overwrite context and lose development progress.

Can I manage risky refactoring safely without polluting my main codebase?

Manage risky refactoring safely by spinning up a dedicated git worktree. This structured workspace isolates experimental changes from the main codebase and enforces safety gates like merge-before-delete to protect unmerged work.