skills.rest
youssefKadaouiAbbassi
youssefKadaouiAbbassiCOMMUNITY
Explore all skills by this author →
GitHub

worktree-task

Manage isolated git worktrees for tasks using EnterWorktree and ExitWorktree commands.

Updated Apr 13, 2026
Search Tags:#git#feature development#worktree#parallel development#task isolation
One-click install
npx skills add https://github.com/youssefKadaouiAbbassi/yka-code --skill worktree-task-youssefkadaouiabbassi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: worktree-task
Source: https://github.com/youssefKadaouiAbbassi/yka-code/tree/main/skills/worktree-task
Command: npx skills add https://github.com/youssefKadaouiAbbassi/yka-code --skill worktree-task-youssefkadaouiabbassi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill isolates tasks using a one-worktree-per-task workflow, preventing file edits from colliding and keeping the main working tree clean.

Core Features & Use Cases

  • Isolated Worktrees: Switch to an isolated git worktree for each task, preventing edit collisions.
  • Net-New Features: Activates by default for net-new features to keep them isolated.
  • Multi-Agent Parallel Tasks: Prevents cross-contamination when multiple concurrent tasks are running.
  • Use Case: When working on a feature or fix, this Skill ensures that your changes are isolated and do not affect the main working tree.

Quick Start

To start a new task in an isolated worktree, simply call 'EnterWorktree <branch-name>'.

Frequently Asked Questions about worktree-task

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

FAQPage Schema
How do I isolate git feature development to prevent file edit collisions?▼

Git worktree isolation prevents file edit collisions by creating a separate working tree for each task. Switching to an isolated worktree keeps your main branch clean while allowing concurrent feature development without cross-contamination.

What is the one-worktree-per-task workflow for parallel development?▼

The one-worktree-per-task workflow assigns an isolated git worktree to each individual task. This approach prevents cross-contamination between concurrent multi-agent workflows and keeps the main working tree clean during feature development.

Can I run multiple concurrent tasks in separate git worktrees?▼

Yes, isolated git worktrees support concurrent multi-agent workflows by preventing cross-contamination. Each task operates in its own worktree, ensuring file edits do not collide or affect the main working tree.

Do I need Claude Code's EnterWorktree command to manage isolated worktrees?▼

Yes, managing isolated worktrees with this workflow requires Claude Code's EnterWorktree and ExitWorktree commands. You start a new task in an isolated worktree by calling EnterWorktree followed by your desired branch name.

When should I use a separate git worktree instead of branching directly?▼

Use a separate git worktree when developing net-new features, fixing bugs, or running concurrent multi-agent tasks. Worktrees prevent file edit collisions and maintain a clean main working tree, which branching alone does not physically isolate.

Related Skills

Explore More Software Engineering Skills→
tom-xstom-xs

using-git-worktrees

Create and manage isolated git worktrees with submodule awareness.

Community
Advanced
dalawwadalawwa

git:worktrees

Manage parallel Git worktrees for multiple branches concurrently.

Community
Advanced
kevindreekevindree

git-workflow-and-versioning

Structures git branching, committing, conflict resolution, and workflow for reviewable code changes.

Community
Intermediate
yurifrlyurifrl
1

git-worktrees

Manage multiple Git worktrees with add, list, remove, and prune commands.

Community
Basic