用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/tomevault-io/skills-registry --skill worktreesnew命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
| Use when this capability is needed.
> Use when this capability is needed.
Review architecture and API design for the vfs-s3 project. Use when the user mentions @architect, asks to review an issue's design, discuss module boundaries, API shape, or architectural decisions for vfs-s3. Also trigger when the user wants to create an ADR (Architecture Decision Record) or evaluate a technical approach for the project. Intended for dispatch from Codex automation or Claude routines; GitHub trigger phrase: @vfs-s3-bot please prepare design doc Use when this capability is needed.
基于 SOC 职业分类
正在显示 SKILL.md
| name | worktreesnew |
| description | Lock worktree after creation Use when this capability is needed. |
| metadata | {"author":"aaronbassett"} |
Create an isolated worktree for parallel development.
<name> - Worktree and branch name (required)--base <branch> - Base branch (default: main)--lock - Lock worktree after creationFirst, check if .worktrees/ is in .gitignore:
grep -q "^\.worktrees" .gitignore 2>/dev/null && echo "OK: .worktrees already gitignored" || echo "MISSING: Need to add .worktrees to gitignore"
If missing, add and commit:
echo ".worktrees/" >> .gitignore
git add .gitignore
git commit -m "chore: add .worktrees to gitignore"
Why gitignore? Each worktree contains a complete checkout. Without gitignoring, you'd accidentally commit nested copies of your entire codebase.
Standard creation (new branch from base):
# Replace <name> with the provided name, <base> with --base value or "main"
git worktree add -b feature/<name> .worktrees/<name> <base>
With lock flag:
git worktree add --lock -b feature/<name> .worktrees/<name> <base>
git worktree list
Expected output shows new worktree:
/path/to/project abc1234 [main]
/path/to/project/.worktrees/<name> abc1234 [feature/<name>]
cd .worktrees/<name>
After creating the worktree:
git push -u origin feature/<name>/worktrees:finish to clean up| Scenario | Command |
|---|---|
| Basic feature | git worktree add -b feature/my-feature .worktrees/my-feature main |
| From release branch | git worktree add -b hotfix/urgent .worktrees/urgent release/v2 |
| Locked worktree | git worktree add --lock -b feature/critical .worktrees/critical main |
| With existing branch | git worktree add .worktrees/existing-branch existing-branch |
Error: fatal: 'branch-name' is already checked out at '/path'
Solution: Each branch can only exist in one worktree. Either:
git worktree listError: fatal: destination path already exists
Solution: The .worktrees/<name> directory exists. Either:
rm -rf .worktrees/<name> && git worktree prune# Create worktree with new branch
git worktree add -b <branch> .worktrees/<name> [base]
# Create worktree with existing branch
git worktree add .worktrees/<name> <branch>
# List worktrees
git worktree list
# Lock/unlock
git worktree lock .worktrees/<name>
git worktree unlock .worktrees/<name>
Converted and distributed by TomeVault — claim your Tome and manage your conversions.