菜单
Create an isolated git worktree under .claude/worktrees/ for a sub-agent to work in. Use this before dispatching any coder agent so that parallel work cannot collide.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/mcorbett51090/RavenClaude --skill new-worktree命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Route everyday, well-defined work (single-file edits, test-writing, summarization, mechanical refactors, boilerplate) to a cheaper coding agent (Grok or Copilot CLI) instead of doing it in the main Claude session, escalating multi-file/architecture/debugging/security work to Claude. Opt-in via the `cheap_lane:` comfort-posture knob.
Authors, validates and packages a claude.ai Organization Skill — the intake questions, the trigger and scope exercises, then lint, pack and verify against measured platform constraints. Reach for this when someone wants to publish a Skill to their organization, or when an upload was rejected and the reason is unclear.
Drafts a reply to an inbound customer email, grounded in the account record and the published help-centre articles rather than in recall. Use when a customer emails about billing, a renewal or an outage, when a reply must cite current policy, or when a teammate asks for a first draft to edit.
| name | new-worktree |
| description | Create an isolated git worktree under .claude/worktrees/ for a sub-agent to work in. Use this before dispatching any coder agent so that parallel work cannot collide. |
Labeling (Sleipnir): in user-facing prose, call this "sending Sleipnir to that branch" — the worktree-traversal labeling convention (see
ravenclaude-core/CLAUDE.md→ "Sleipnir"). Labeling only; the mechanics below (git worktree) are unchanged.
role — one of: architect, backend-coder, frontend-coder, fullstack-coder, tester.slug — short kebab-case identifier of the task (e.g. auth-refresh, nav-redesign).base — branch to fork from. Default: main.^[a-z0-9][a-z0-9-]{1,40}$. Reject otherwise..claude/worktrees/<role>-<slug>/agent/<role>/<slug>git fetch origin <base> so the worktree starts from current upstream.git worktree add -b agent/<role>/<slug> .claude/worktrees/<role>-<slug> origin/<base>
pnpm install), run it once in the new worktree before handing off.After create, write the lane stamp (plugins/ravenclaude-core/scripts/write-lane-stamp.sh <dest> <task> <branch> <created_by>) and open a dedicated VS Code window (rcwt new / code -n <path>). Never add the new worktree as a second folder in an existing window — multi-root pools Chat context. Do not restyle the sub-agent procedure above.
Worktrees are NOT auto-removed. Use cleanup-worktrees when the task is integrated.
Two parallel coder agents on the same working tree will silently corrupt each other's diffs. Worktrees are cheap; recovery from a stomped diff is not.
isolation: "worktree"?The Agent tool's native worktree isolation is a one-off, ephemeral worktree that gets cleaned up automatically when the sub-agent makes no changes. This skill is for the Team Lead's managed worktrees that persist across sub-agent runs: predictable paths under .claude/worktrees/<role>-<slug>/, predictable branch names agent/<role>/<slug>, and tracked by cleanup-worktrees so they don't accumulate silently. Use the native isolation for fire-and-forget exploration; use this skill when the worktree is part of a multi-step Team Lead workflow that needs to be visible to subsequent agents.