菜单
Use when starting feature implementation, plan execution, or risky edits that should be isolated. Detects existing isolation, prefers native worktree tools, and falls back to manual git worktrees only when no native tool exists.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/wfprieto/wcbs-build-kit --skill using-git-worktrees命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when a WCBS plan, remediation backlog, migration, release, or multi-slice engineering objective has dependent work that requires requirement-to-node traceability, topology validation, READY-frontier scheduling, or evidence-backed node locking. Also activate when the user explicitly requests /graph execution.
Use when the task involves any build, fix, audit, debug, optimization, release, verification, prompt, skill, or agent-design task. Activates the APIVR lifecycle and Elite Build Goals guardrails from this repository before task-specific work.
Use when a build, fix, plan, audit, skill, agent, or pipeline has more than one viable design and the agent must choose the simplest safe option or challenge unjustified complexity.
基于 SOC 职业分类
正在显示 SKILL.md
| name | using-git-worktrees |
| description | Use when starting feature implementation, plan execution, or risky edits that should be isolated. Detects existing isolation, prefers native worktree tools, and falls back to manual git worktrees only when no native tool exists. |
| activation | Activate when the description trigger applies to the current task. |
| required_inputs | Task request, relevant repository context, constraints, and authority dependencies. |
| required_outputs | Skill-specific artifact, verification evidence, canonical verdict, and next action. |
| authority_dependencies | 00_start_here/SOURCE_OF_TRUTH.md; 10_governance/APIVR_EXECUTION_LIFECYCLE.md; 10_governance/source_of_truth/Elite_Build_Goals_v3.md. |
| evidence_requirements | Executed checks or an honest Unknown, Not Run, or Blocked state for every material claim. |
Ensure work happens in an isolated workspace when risk, scope, or user preference warrants it.
Core rule: detect existing isolation first, prefer native tools second, use manual git worktrees only as fallback.
Before creating or entering a worktree:
50_audits/AUDIT_TIER_ROUTER.md.Run the platform-equivalent of:
GIT_DIR=$(cd "$(git rev-parse --git-dir)" 2>/dev/null && pwd -P)
GIT_COMMON=$(cd "$(git rev-parse --git-common-dir)" 2>/dev/null && pwd -P)
BRANCH=$(git branch --show-current)
SUBMODULE_ROOT=$(git rev-parse --show-superproject-working-tree 2>/dev/null)
Interpretation:
GIT_DIR != GIT_COMMON and SUBMODULE_ROOT is empty, you are already in a linked worktree. Do not create another one.If no existing isolation is detected:
Use native harness/workspace tools before manual git commands. Look for tools or commands such as:
EnterWorktreeWorktreeCreate/worktree--worktreeThe user's consent to create an isolated workspace authorizes the native isolation tool.
Never use git worktree add when a native tool is available.
Use this only when no native tool exists.
Directory priority:
.worktrees/;worktrees/;.worktrees/ at project root.Before creating a project-local worktree, verify the directory is ignored:
git check-ignore -q .worktrees 2>/dev/null || git check-ignore -q worktrees 2>/dev/null
If it is not ignored, add it to .gitignore and commit that safety change before creating nested worktree contents.
Create fallback worktree:
git worktree add ".worktrees/<branch-name>" -b "<branch-name>"
cd ".worktrees/<branch-name>"
If sandbox or filesystem permissions block creation, report the blocker and work in place only with user approval.
Run project setup and baseline checks appropriate to the project:
npm install / npm testcargo build / cargo testpip install -r requirements.txt / pytestgo mod download / go test ./...If baseline checks fail, record them as existing evidence and ask before proceeding.
Whoever created the worktree owns cleanup.
.worktrees/ or worktrees/: this kit may remove it after merge or discard.For local merge cleanup, use this order:
git worktree prune.For PR flow, do not clean up the worktree until PR iteration is complete.
When implementation is complete, use skills/finishing-a-development-branch/SKILL.md before merge, PR, keep, discard, or cleanup decisions.
git status --short --branch
git worktree list --porcelain
git check-ignore -q .worktrees || printf '.worktrees/ must be ignored before creating it\n'
git worktree add ".worktrees/feature-v2" -b feature/v2
If git worktree list --porcelain shows the current path is already a linked
worktree, stop before the add command. If the project has a native worktree
tool, use that tool instead of the fallback command and record its ownership.
Never:
Verify repository state and ownership, create the isolated worktree with the native Git command, record its branch and baseline, then remove it only after the merge or explicit discard decision is proven.