菜单
Create a new git worktree from origin/trunk in ~/worktrees.nosync and copy node_modules. Use when the user wants to "create a worktree", "new worktree", "start a worktree branch", or needs an isolated working directory for a feature branch.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user wants to name or rename something — a product, feature, brand, project, command, or company — or asks to "brainstorm names", "find a better name", "naming ideas", or invokes /brainstorming-names.
Use when a task has a large solution space and a measurable quality signal and the goal is to generate many candidates and select the best — naming/branding, UX/UI variants, marketing copy, code optimization, prompt tuning. Triggers: "brainstorm and pick the best", "explore and exploit", "simulated annealing", "tournament of options", "generate N options and rank them", iterate-until-score loops, or /explore-exploit.
Use when the user asks to rate, score, judge, critique with a number, or "how good is" an artifact — a live website/UI, a markdown draft (blog post, README, plan, docs), or code/a diff — or invokes /score, or sets up an iterate-until-score-N feedback loop (e.g. with /goal "repeat until 9/10").
Start work on a Linear issue end-to-end — create a worktree, fetch issue context from Linear, implement the fix, then commit, push, and open a draft PR. Use when the user says "start issue", "work on STU-1234", "create a worktree and fix <Linear link>", "start a worktree for this ticket", or gives a Linear URL/issue id and wants the whole branch→PR flow.
Use when the user wants to undo, absorb, collapse, or reverse a git worktree — "undo worktree", "absorb worktree", "move worktree branch back to main repo", "remove worktree and checkout in main", "get rid of this worktree", or finish work in a ~/worktrees.nosync worktree and continue it in the main studio checkout.
This skill should be used when the user asks to "clean up my Mac", "free disk space", "my disk is full", "what's taking up space", "reclaim storage", "offload files", or wants to dedupe/archive backups and media to remote storage. Provides a scan → categorize → offload/clean → reclaim workflow with tested scripts and macOS-specific gotchas.
| name | worktree |
| description | Create a new git worktree from origin/trunk in ~/worktrees.nosync and copy node_modules. Use when the user wants to "create a worktree", "new worktree", "start a worktree branch", or needs an isolated working directory for a feature branch. |
| user-invocable | true |
Create a new git worktree based on origin/trunk in ~/worktrees.nosync, with node_modules copied from the current directory for fast setup.
Gather information:
Fetch latest from origin:
git fetch origin trunk
Create the worktree directory if needed:
mkdir -p ~/worktrees.nosync
Create the worktree with new branch:
git worktree add ~/worktrees.nosync/<branch-name> -b <branch-name> origin/trunk
Copy node_modules if it exists in the source directory:
cp -R ./node_modules ~/worktrees.nosync/<branch-name>/node_modules
Note: This can take a moment for large node_modules directories.
Report success with the path to the new worktree:
Worktree created at: ~/worktrees.nosync/<branch-name>
If the user doesn't specify a branch name, suggest a format based on context:
feature/<short-description>fix/<issue-id> or fix/<short-description>stu-<ticket-number>-<short-description> (for Studio)After completing work, remind the user they can remove the worktree with:
git worktree remove ~/worktrees.nosync/<branch-name>