Tools to create, manage, and delete isolated git worktrees to run parallel development sessions without port or data conflicts.
Install
mkdir -p .claude/skills/wt-llama-farm && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11864" && unzip -o skill.zip -d .claude/skills/wt-llama-farm && rm skill.zipInstalls to .claude/skills/wt-llama-farm
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Manage LlamaFarm worktrees for isolated parallel development. Create, start, stop, and clean up worktrees.Key capabilities
- →Create isolated development environments using git worktrees.
- →Start and stop services within a worktree.
- →List all worktrees with their status and port assignments.
- →Clean up orphaned data and worktrees.
- →Diagnose common issues in worktrees.
How it works
The skill manages isolated LlamaFarm development environments by creating git worktrees, each with its own services, ports, and data directories, allowing parallel agent sessions without conflicts.
Inputs & outputs
When to use wt
- →Create an isolated environment for a feature branch
- →Run multiple agent sessions simultaneously
- →Clean up orphaned data or worktrees
- →Check service health across worktrees
About this skill
wt - Worktree Manager Skill
Manages isolated LlamaFarm development environments using git worktrees. Each worktree has its own services, ports, and data directories - enabling parallel agent sessions without conflicts.
Full Documentation
For complete documentation, architecture details, and advanced usage: @scripts/wt/README.md
Quick Reference
| Task | Command |
|---|---|
| Create worktree and start services | wt create feat/my-feature |
| Create and cd into worktree | wt create --go feat/my-feature |
| List all worktrees with status | wt list |
| Check service health | wt status or wt health |
| Start/stop services | wt start / wt stop |
| View service logs | wt logs [server|rag|runtime|designer|all] |
| Delete worktree | wt delete <name> |
| Switch to worktree | wt switch <name> |
| Open Designer in browser | wt open |
| Diagnose issues | wt doctor |
| Clean orphaned data | wt gc |
When to Use wt
Use wt when:
- Starting isolated work on a feature/task that needs running services
- Running parallel coding sessions (multiple agents or terminals)
- Testing changes without affecting the main development environment
- Avoiding port conflicts between concurrent LlamaFarm instances
Common Workflows
Starting a New Task
# Create isolated environment with services running
wt create --go feat/my-task
# Work in the worktree...
# Services are already running on auto-assigned ports
# Check status anytime
wt status
# View logs if needed
wt logs server
Checking What's Running
# List all worktrees with their port assignments
wt list
# Example output:
# NAME STATUS SERVER DESIGNER RUNTIME
# feat-my-task running 8150 5150 11150
# fix-bug stopped 8234 5234 11234
Cleaning Up
# Stop services and remove a worktree
wt delete feat-my-task
# Remove data for worktrees that no longer exist
wt gc
# Remove worktrees for branches merged to main
wt prune
Troubleshooting
# Diagnose common issues (ports, stale PIDs, missing tools)
wt doctor
# Restart stuck services
wt stop && wt start
# Force delete if normal delete fails
wt delete my-worktree --force
Service URLs
Each worktree gets unique ports. Check URLs with:
wt url
# Outputs:
# Server: http://localhost:8150
# Designer: http://localhost:5150
# Runtime: http://localhost:11150
If the Caddy proxy is running, use port-free URLs:
http://server.feat-my-task.localhost
http://designer.feat-my-task.localhost
Key Environment Details
- Worktrees location:
~/worktrees/llamafarm/ - Data directories:
~/.llamafarm/worktrees/<name>/ - Port allocation: Deterministic hash of worktree name (14345+offset, 5000+offset, 11000+offset)
- Logs:
~/.llamafarm/worktrees/<name>/logs/
Notes for the Agent
- Always use
wt create --gowhen setting up a new task environment - it handles everything (branch, deps, build, services) - Check
wt listfirst before creating a new worktree to see what already exists - Use
wt statusto verify services are healthy before running tests or making API calls - Run
wt doctorwhen encountering unexplained service issues - Clean up with
wt deletewhen a task is complete to free resources
When not to use it
- →When isolated development environments are not needed.
- →When conflicts between parallel agent sessions are not a concern.
- →When manual management of git worktrees is preferred.
Limitations
- →Worktrees are located in `~/worktrees/llamafarm/`.
- →Data directories are in `~/.llamafarm/worktrees/<name>/`.
- →Port allocation is based on a deterministic hash of the worktree name.
How it compares
This skill provides a centralized command-line interface for managing multiple isolated git worktrees with their own services and data, simplifying parallel development compared to manual git worktree operations.
Compared to similar skills
wt side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| wt (this skill) | 0 | 6mo | Review | Intermediate |
| create-worktree-skill | 2 | 9mo | No flags | Intermediate |
| makefile-dev-workflow | 0 | 6mo | Review | Beginner |
| terminal | 0 | 1mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by llama-farm
View all by llama-farm →You might also like
create-worktree-skill
disler
Use when the user explicitly asks for a SKILL to create a worktree. If the user does not mention "skill" or explicitly request skill invocation, do NOT trigger this. Only use when user says things like "use a skill to create a worktree" or "invoke the worktree skill". Creates isolated git worktrees with parallel-running configuration.
makefile-dev-workflow
raphaelmansuy
Unified development workflow for EdgeQuake using Makefile commands. Use when starting services, running tests, or managing the full development stack (database, backend, frontend). Provides simplified alternatives to raw cargo/npm commands.
terminal
fisker086
Execute shell commands on the server
bazel-build-optimization
wshobson
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
github-actions-templates
wshobson
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
linux-production-shell-scripts
davila7
This skill should be used when the user asks to "create bash scripts", "automate Linux tasks", "monitor system resources", "backup files", "manage users", or "write production shell scripts". It provides ready-to-use shell script templates for system administration.