skills.rest
igrekplus
igrekplusCOMMUNITY
Explore all skills by this author →
GitHub

parallel_worktree

Coordinate AI sessions across branches and worktrees with naming rules.

Updated Aug 23, 2026
Search Tags:#git-worktree#branching-strategy#workflow-coordination#conflict-prevention#parallel-worktree#ai-session-management
One-click install
npx skills add https://github.com/igrekplus/football-delay-watching --skill parallel-worktree
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: parallel_worktree
Source: https://github.com/igrekplus/football-delay-watching/tree/main/.agent/skills/parallel_worktree
Command: npx skills add https://github.com/igrekplus/football-delay-watching --skill parallel-worktree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures multiple AI sessions can operate on the same repository without conflicts by enforcing one session per branch per worktree, using dedicated directories, and clear ownership rules.

Core Features & Use Cases

  • Enforces 1 session per branch per worktree to prevent cross-session contamination.
  • Defines consistent naming conventions for branches (feature-<issue-number>/<task-slug>) and worktrees (../football-delay-watching-<issue-number>-<task-slug>).
  • Provides guidance to coordinate investigations, experiments, and implementations with isolated workspaces and controlled handoffs.

Quick Start

Configure your environment to create separate branches and worktrees per issue, then assign each AI session to its own workspace and track changes independently.

Frequently Asked Questions about parallel_worktree

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

FAQPage Schema
How do I run multiple AI sessions on the same Git repository without conflicts?▼

To run parallel AI sessions safely, assign one session per branch per worktree. This isolation prevents cross-session contamination by giving each session its own dedicated workspace and branch to operate on.

What is the best way to manage Git worktrees for parallel development tasks?▼

The best way to manage Git worktrees is using deterministic naming rules for branches and directories, such as feature-<issue-number>/<task-slug>. This ensures clear ownership and prevents overlapping work across different tasks.

How do you coordinate handoffs between isolated Git worktree sessions?▼

Coordinate worktree session handoffs by requiring explicit pull requests before merging. This controlled handoff process ensures changes from isolated branches are reviewed and integrated safely without disrupting other ongoing work.

When do I need to use isolated worktrees for AI-assisted coding?▼

You need isolated worktrees whenever parallel exploration is required on the same repository for different issues, investigations, or experiments. This prevents file conflicts when multiple sessions attempt to modify code simultaneously.

Does using parallel worktrees require a specific branching strategy?▼

Yes, using parallel worktrees requires a strict branching strategy where each session gets a dedicated branch with consistent naming conventions. This enforces one session per branch to maintain clear workspace ownership and avoid conflicts.

Related Skills

Explore More Software Engineering Skills→
Terry-MaoTerry-Mao
144

git-worktree

Create isolated Git worktrees for parallel branch work with naming and safety checks.

Community
Advanced
vstorm-covstorm-co
1.0k

git-workflow

Manage git commits, branches, pull requests, and conflict resolution.

Official
Intermediate
rigercrigerc

td-task-management

Coordinate and track AI agent tasks across context windows.

Community
Advanced
itallstartedwithaideaitallstartedwithaidea
31

git-worktrees

Create and manage isolated Git worktree directories for concurrent development tasks.

Community
Intermediate