メニュー
Git worktree management for isolated parallel development. Handles creating, listing, switching, and cleaning up worktrees with interactive confirmations, automatic .env copying, and .gitignore management. Follows KISS principles.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/dlabs/claude-marketplace --skill git-worktreeコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Production A/B testing lifecycle for design variants. Covers hypothesis formation, feature flags, variant comparison, analytics tracking, statistical significance analysis, experiment setup, and cleanup.
Browser automation using Vercel's agent-browser CLI. Use when you need to interact with web pages, fill forms, take screenshots, or scrape data. Uses Bash commands with ref-based element selection. Triggers on "browse website", "fill form", "click button", "take screenshot", "scrape page", "web automation".
Multi-agent architecture review combining core architecture design with parallel security, performance, and data integrity assessments. Produces ADRs in MADR format. Covers ADR, architecture decision, system design, scalability assessment. Not for code review or implementation — for architectural decisions only.
SOC 職業分類に基づく
SKILL.md を表示中
| name | git-worktree |
| description | Git worktree management for isolated parallel development. Handles creating, listing, switching, and cleaning up worktrees with interactive confirmations, automatic .env copying, and .gitignore management. Follows KISS principles. |
| allowed-tools | Bash |
| argument-hint | [create|list|cleanup] [branch-name] |
!git worktree list 2>/dev/null || echo "Not a git repository or git not available."
Unified interface for managing Git worktrees across your development workflow. Whether reviewing PRs in isolation or working on features in parallel, this skill handles all the complexity.
.worktrees/ directoryNEVER call git worktree add directly. Always use the worktree-manager.sh script.
The script handles critical setup that raw git commands don't:
.env, .env.local, .env.test, etc. from main repo.worktrees is in .gitignore# CORRECT - Always use the script
bash ${CLAUDE_SKILL_DIR}/scripts/worktree-manager.sh create feature-name
# WRONG - Never do this directly
git worktree add .worktrees/feature-name -b feature-name main
/blueprint-dev:bp:review): If NOT already on the target branch, offer worktree for isolated review/blueprint-dev:bp:build): Ask if user wants parallel worktree or live branch workcreate <branch-name> [from-branch]Creates a new worktree with the given branch name.
branch-name (required): Name for the new branch and worktreefrom-branch (optional): Base branch to create from (defaults to main)bash ${CLAUDE_SKILL_DIR}/scripts/worktree-manager.sh create feature-login
bash ${CLAUDE_SKILL_DIR}/scripts/worktree-manager.sh create feature-auth develop
What happens:
list or lsLists all available worktrees with their branches and current status.
bash ${CLAUDE_SKILL_DIR}/scripts/worktree-manager.sh list
switch <name> or go <name>Switches to an existing worktree.
bash ${CLAUDE_SKILL_DIR}/scripts/worktree-manager.sh switch feature-login
If name not provided, lists available worktrees and prompts for selection.
copy-env [name] or env [name]Copies .env files from main repo to an existing worktree. If name is omitted and you're inside a worktree, copies to the current worktree.
bash ${CLAUDE_SKILL_DIR}/scripts/worktree-manager.sh copy-env feature-login
bash ${CLAUDE_SKILL_DIR}/scripts/worktree-manager.sh copy-env # copies to current worktree
cleanup or cleanInteractively cleans up inactive worktrees with confirmation.
bash ${CLAUDE_SKILL_DIR}/scripts/worktree-manager.sh cleanup
What happens:
/blueprint-dev:bp:review1. Check current branch
2. If ALREADY on target branch → stay there, no worktree needed
3. If DIFFERENT branch → offer worktree:
"Use worktree for isolated review? (y/n)"
- yes → call git-worktree skill to create worktree
- no → proceed with PR diff on current branch
/blueprint-dev:bp:build1. Ask: "How do you want to work?"
1. New branch on current worktree (live work)
2. Worktree (parallel work)
2. If choice 1 → create new branch normally
3. If choice 2 → call git-worktree skill to create from main
# Create isolated worktree for review (copies .env files)
bash ${CLAUDE_SKILL_DIR}/scripts/worktree-manager.sh create pr-123-feature-name
cd .worktrees/pr-123-feature-name
# After review, return to main and clean up
cd ../..
bash ${CLAUDE_SKILL_DIR}/scripts/worktree-manager.sh cleanup
# Start first feature
bash ${CLAUDE_SKILL_DIR}/scripts/worktree-manager.sh create feature-login
# Start second feature
bash ${CLAUDE_SKILL_DIR}/scripts/worktree-manager.sh create feature-notifications
# List and switch between them
bash ${CLAUDE_SKILL_DIR}/scripts/worktree-manager.sh list
bash ${CLAUDE_SKILL_DIR}/scripts/worktree-manager.sh switch feature-login
The script will ask if you want to switch to it instead.
Switch out of the worktree first:
cd $(git rev-parse --show-toplevel)
bash ${CLAUDE_SKILL_DIR}/scripts/worktree-manager.sh cleanup
Copy them manually:
bash ${CLAUDE_SKILL_DIR}/scripts/worktree-manager.sh copy-env feature-name
.worktrees/
├── feature-login/ # Worktree 1
│ ├── .git
│ ├── app/
│ └── ...
├── feature-notifications/ # Worktree 2
│ ├── .git
│ ├── app/
│ └── ...
.gitignore (updated to include .worktrees)
git worktree add for isolated environments