worktree-wizard-integration

Integrate worktree-wizard to automate per-branch port offsets and data isolation.

1|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/asabedia/worktree-wizard --skill worktree-wizard-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktree-wizard-integration
Source: https://github.com/asabedia/worktree-wizard/tree/main/plugin/skills/worktree-wizard-integration
Command: npx skills add https://github.com/asabedia/worktree-wizard --skill worktree-wizard-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Onboarding multi-branch projects with Docker often leads to port conflicts and mixed data across branches. This skill automates the integration of worktree-wizard to provide per-branch worktrees with automatically offset ports and isolated data directories.

Core Features & Use Cases

  • Automatic port offset calculation using wt.base-port labels to map host ports per worktree.
  • Per-slot data isolation with dedicated .worktrees and .docker-data directories.
  • Simplified integration through justfile imports and reference patterns for common frameworks.

Quick Start

Run the onboarding wizard to generate per-branch worktrees and offset ports for your Docker setup.

Frequently Asked Questions about worktree-wizard-integration

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

FAQPage Schema
How do I prevent Docker port conflicts when working with multiple git worktrees?

Prevent Docker port conflicts across git worktrees by applying wt.base-port labels to automatically calculate and offset host ports for each branch. This ensures isolated environments run simultaneously without network collisions.

How do I set up isolated data directories for Docker worktrees in my project?

Set up isolated data directories for Docker worktrees by integrating wt.data-dir configurations. This creates dedicated .worktrees and .docker-data folders for each branch, separating database and storage volumes automatically.

Can I use justfile imports to automate per-branch Docker environments?

Yes, you can use justfile imports to automate per-branch Docker environments. Standard justfile imports integrate seamlessly with worktree-wizard, providing cohesive development workflows for managing isolated ports and data directories.

What's the best way to onboard an existing project to automated per-branch worktrees?

The best way to onboard an existing project is running the integration wizard to apply wt.base-port and wt.data-dir labels. This automates per-branch port offsets and data isolation without disrupting your current Docker setup.

Why does my Docker data get mixed across feature branches using worktrees?

Docker data gets mixed across feature branches because worktrees lack isolated data directories. Enforce wt.data-dir labels to allocate dedicated .docker-data paths per branch, ensuring complete data separation.