worktree-flow

Isolate tasks in separate git worktrees and automate PR creation.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/JNZader/javi-ai --skill worktree-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktree-flow
Source: https://github.com/JNZader/javi-ai/tree/main/own/skills/worktree-flow
Command: npx skills add https://github.com/JNZader/javi-ai --skill worktree-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Isolate each task in separate git worktrees to enable parallel AI agent execution while keeping the main worktree clean and reducing merge conflicts.

Core Features & Use Cases

  • Parallel task isolation: Each task runs in its own worktree with its own branch.
  • Automated PR creation: Automatically pushes branches and creates PRs after task completion.
  • Wave-based execution: Supports executing tasks in waves with controlled concurrency.

Quick Start

Configure the base_dir, branch_prefix, and max_concurrent in your ai-config, then run the wave executor to spawn parallel task worktrees.

Frequently Asked Questions about worktree-flow

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

FAQPage Schema
How do I run parallel AI agent workflows in isolated git worktrees?

Using parallel git worktrees isolates each task in its own branch and directory, keeping your main worktree clean while enabling concurrent AI agents to execute without merge conflicts.

What is the best way to automate PR creation for parallel git branches?

Automating PR creation for parallel branches is achieved by a lifecycle workflow that pushes completed branches and opens pull requests automatically after task validation, toggled via the auto_pr configuration.

How do I control concurrency for wave-based task execution in git?

You control wave-based execution concurrency by setting the max_concurrent parameter, which limits the number of parallel task worktrees running simultaneously during the orchestration lifecycle.

Can I configure the base directory and branch prefix for automated worktree workflows?

Yes, you can specify the base_dir and branch_prefix in your configuration to define where parallel worktrees are created and how their isolated branches are named.

Does worktree-flow support automated cleanup after PR publishing?

Yes, the orchestration lifecycle includes optional cleanup after worktree creation, task execution, validation, and PR publishing are complete to manage system resources.

Why use separate git worktrees for multi-task AI orchestration?

Using separate worktrees provides strict task isolation and clean history for multi-task workflows, preventing agents from overwriting each other's changes and reducing merge conflicts.