Dispatches tasks into new git worktrees using workmux with generated prompt files.
npx skills add https://github.com/wesbragagt/nixos-config --skill worktree-wesbragagt
Please help me install this Agent Skill. Skill: worktree Source: https://github.com/wesbragagt/nixos-config/tree/main/home/skills/worktree Command: npx skills add https://github.com/wesbragagt/nixos-config --skill worktree-wesbragagt
workmux add <name> -b -P <file> to create one worktree per task. - Skill delegation: Pass skill references like /auto or /plan-review (with flags) through to the worktree agent instead of writing manual implementation steps. - Workflow flags: Use --merge to have the agent commit, rebase, and merge via the /merge skill, or --fork to copy the current conversation context into the new worktree. - Use Case: You have three independent bug fixes. Invoke the skill with all three tasks; it writes three prompt files and creates three worktrees, each with its own branch and agent. ## Quick Start Ask the assistant to launch your tasks in new git worktrees using the worktree skill, optionally with --merge or --fork flags.High-intent search queries and answers about installing and using this skill.
Pass your tasks to the worktree skill, which writes a detailed prompt file per task and runs workmux add for each one. Every task gets its own worktree and branch, so agents work independently without conflicts.
workmux is a tool for creating git worktrees, invoked here via workmux add <name> -b -P <prompt-file>. The skill generates a kebab-case worktree name and a temp prompt file, then runs the command from the current directory so the new worktree branches from the checked-out branch.
Yes. Include the skill reference in your request and the dispatcher writes it into the prompt file, including any flags like --gemini. The worktree agent then executes that skill instead of following manual implementation steps.
The --fork flag copies the current conversation into the new worktree so the agent resumes with full context. The prompt is prepended with instructions preventing the forked agent from recursively dispatching more worktrees.
Avoid it when tasks are tightly coupled or must share uncommitted state, since each worktree is an isolated checkout. It is also unnecessary for a single small change you can implement directly in the current branch.
Base-AnaliticaExecutes implementation plans by dispatching fresh subagents per task with per-task reviews.
The-Vibe-CompanyResolves in-progress git merge and rebase conflicts while preserving both change intents.
FlorianBruniauxOrchestrates a five-stage plan-to-execution pipeline from product review to merged PR.
linehaul-aiCreate and switch isolated Git worktrees via worktree-manager.sh.