meow:worktree

Create isolated git worktrees for parallel agents and merge results.

14|2|Updated Mar 25, 2026

Search Tags:#automation #git #orchestration #worktree #parallel #version-control

Ready to run

npx skills add https://github.com/ngocsangyem/MeowKit --skill meow-worktree

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: meow:worktree
Source: https://github.com/ngocsangyem/MeowKit/tree/main/.claude/skills/meow%3Aworktree
Command: npx skills add https://github.com/ngocsangyem/MeowKit --skill meow-worktree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git worktree management for parallel agent execution. Creates isolated worktrees for parallel agents to prevent file conflicts, simplifies result merging, and provides safe cleanup after tasks complete.

Core Features & Use Cases

Create an isolated worktree for a parallel agent on a dedicated branch (e.g., parallel/{agent}-{timestamp}) to avoid conflicts with other agents.
Merge a completed worktree back to the feature branch using a no-fast-forward merge and report conflicts for human resolution.
Cleanup worktree directories and the associated parallel branch after successful merges, ensuring no uncommitted changes remain.

Quick Start

Create an isolated worktree for a specific parallel agent on a timestamped branch and merge results back to the feature branch after completion.

Frequently Asked Questions about meow:worktree

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

FAQPage Schema

How do I run parallel git agents without file conflicts?▼

Git worktrees prevent file conflicts during parallel agent execution by creating isolated working directories on dedicated branches. Each agent operates independently, avoiding overlapping file modifications and simplifying result merging.

How do I merge parallel git branches back into a feature branch?▼

Merging parallel git branches back into a feature branch uses a no-fast-forward merge to preserve the parallel work history. If conflicts occur during the merge, the process halts and reports them for human resolution before cleanup.

Can I create a git worktree directly on the main branch?▼

No, you cannot create a git worktree directly on the main or master branch. The orchestration process requires creating worktrees on dedicated parallel branches to ensure safe isolation and prevent direct modifications to the primary branch.

What is the best way to clean up git worktrees after merging parallel tasks?▼

The best way to clean up git worktrees after merging is to remove the worktree directory and delete the associated parallel branch. This safe cleanup only occurs after a successful merge and ensures no uncommitted changes remain.

Do I need a complex task structure to use git worktree orchestration?▼

Yes, git worktree orchestration is designed for complex tasks that decompose into parallel subtasks. It assigns per-agent worktrees and centralizes the merging process, making it unnecessary for simple linear workflows.