用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/raine/skills --skill worktree命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | worktree |
| description | Launch one or more tasks in new git worktrees using workmux. |
| allowed-tools | Bash, Write |
Launch one or more tasks in new git worktrees using workmux.
Tasks: $ARGUMENTS
HARD RULE — NO EXCEPTIONS: Do NOT explore, read, grep, glob, or search the
codebase. Do NOT use the Task/Explore agent. Do NOT investigate the problem. You
are a thin dispatcher — your ONLY job is to write prompt files and run
workmux add. The worktree agent will do all the exploration and implementation.
If the user's message contains enough context to write a prompt, write it immediately. If not, ask the user for clarification — do NOT try to figure it out by reading code.
If tasks reference earlier conversation (e.g., "do option 2"), include all relevant context in each prompt you write.
If tasks reference a markdown file (e.g., a plan or spec), re-read the file to ensure you have the latest version before writing prompts.
For each task:
workmux add <worktree-name> -b -P <temp-file> to create the worktreeThe prompt file should:
task <id> start before beginning work to mark it activeIf the user passes a skill reference (e.g., /auto, /plan-review),
the prompt should instruct the agent to use that skill instead of writing out
manual implementation steps.
Skills can have flags. If the user passes /auto --gemini, pass the
flag through to the skill invocation in the prompt.
Example prompt:
[Task description here]
Use the skill: /skill-name [flags if any] [task description]
Before starting, run `task <id> start` to mark it active.
After completion, run `task <id> done` to mark it complete.
Do NOT write detailed implementation steps when a skill is specified — the skill handles that.
--merge: When passed, add instruction to use /merge skill at the end to
commit, rebase, and merge the branch.
...
Then use the /merge skill to commit, rebase, and merge the branch.
Only instruct worktree agent to /merge if explicitly requested by user in
task.
--fork: When passed, add --fork to the workmux add command. This copies
the current conversation into the new worktree so the agent resumes with full
context of what was discussed. Useful when the current conversation has built up
context that the new worktree agent needs.
When --fork is used, prepend this to the prompt file so the forked agent does
not recursively dispatch more worktrees:
You are now running INSIDE a git worktree created by the /worktree skill. The
prior conversation context (including any /worktree dispatch instructions) is
ancestry only. Do NOT invoke the /worktree skill, do NOT run `workmux add`, and
do NOT create further worktrees. Your job is to implement the task below
directly in this worktree.
Write ALL temp files first, THEN run all workmux commands.
IMPORTANT: Run workmux add from the CURRENT directory. Do NOT cd to the
main repo or any other directory. The new worktree branches from whatever branch
is checked out in the current directory.
Step 1 - Write all prompt files (in parallel):
tmpfile=$(mktemp).md
cat > "$tmpfile" << 'EOF'
Implement feature X...
EOF
echo "$tmpfile" # Note the path for step 2
Step 2 - After ALL files are written, run workmux commands (in parallel):
workmux add feature-x -b -P /tmp/tmp.abc123.md
workmux add feature-y -b -P /tmp/tmp.def456.md
After creating the worktrees, inform the user which branches were created.
Remember: Your task is COMPLETE once worktrees are created. Do NOT implement anything yourself.