maestro-fork

Create and synchronize session-specific git worktrees for parallel development.

76|5|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/catlog22/pi-maestro-flow --skill maestro-fork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maestro-fork
Source: https://github.com/catlog22/pi-maestro-flow/tree/main/.pi/skills/maestro-fork
Command: npx skills add https://github.com/catlog22/pi-maestro-flow --skill maestro-fork

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates or synchronizes a session-specific git worktree so parallel development can happen safely without disturbing the main branch or other active sessions.

Core Features & Use Cases

  • Session worktree creation: Fork a session into its own branch and workspace for isolated implementation.
  • Worktree synchronization: Merge the latest main changes into an existing session worktree when you need to stay current.
  • Registry and scope management: Update session scope markers, scoped state, and shared worktree registries so the workflow remains traceable and consistent.

Quick Start

Create a session worktree for the specified session ID and optional base ref, then confirm the scope and registry updates when prompted.

Frequently Asked Questions about maestro-fork

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

FAQPage Schema
How do I use git worktrees for parallel development across multiple sessions?

Git worktrees for parallel development let you create isolated branches in separate directories, so multiple sessions can progress safely without disturbing the main branch or other active sessions.

What is the best way to synchronize a git worktree with latest main branch changes?

Synchronizing a git worktree merges the latest main branch changes into your existing session workspace, using conflict-aware recovery and validation gates to keep parallel development up to date safely.

Can I scope session state and manage worktree registries for isolated git branches?

Yes, you can update session scope markers, scoped state, and shared worktree registries during worktree creation, ensuring your parallel development workflow remains traceable and consistent across sessions.

How does a session-specific git worktree handle conflicts when syncing parallel branches?

Session-specific git worktrees handle sync conflicts through conflict-aware recovery, applying validation gates and requiring user confirmation before registry writes to prevent data loss during branch synchronization.

When do I need an isolated git worktree for multi-session coding workflows?

You need an isolated git worktree for multi-session coding workflows when parallel development requires scoped state, separate branches, and shared artifact copying without risking interference between active sessions.