Menu
Use when managing Git worktrees with `git wt` or `git worktree`, especially for branch isolation, `.worktrees/` layout, parallel work, or diagnosing worktree create/remove errors.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | git-worktree |
| description | Use when managing Git worktrees with `git wt` or `git worktree`, especially for branch isolation, `.worktrees/` layout, parallel work, or diagnosing worktree create/remove errors. |
Use git wt for normal list, switch/create, rename, and delete flows. Drop to native git worktree only when you need low-level cleanup or diagnosis.
This skill owns command syntax and troubleshooting. It does not decide whether a new isolated workspace should be created for feature work; use using-git-worktrees for that workflow decision. PR 作成から統合までの一連フローや、追加ディレクトリ不要の通常ブランチ運用はこのスキルの対象外。
git wt で既存 worktree と使用中ブランチを確認するgit config --local wt.basedir ".worktrees" を確認するgit wt
git wt --json
git wt <name> switches to an existing worktree when it exists, otherwise creates a worktree and branch.
git wt feature/my-task
git wt feature/my-task origin/main
git wt -b feature/my-task my-task
git wt -m old-name new-name
git wt -M old-name new-name
git wt -d feature/my-task
git wt -D feature/my-task
git worktree prune -v
git wt --json
git worktree list
./scripts/check-worktree-config.sh
wt.basedir は repo-local にそろえるgit worktree prune を忘れない.env などローカルファイル配布が必要な時だけ wt.copy / --copy を使うgit wt <worktree> と git wt -b <branch> <worktree> の意味を混同する.worktrees/ 前提を global config だけで済ませるreferences/git-wt-commands.md — git wt の正確なフラグ・全コマンドが必要な時に読むreferences/configuration.md — wt.basedir / wt.copy など repo 設定の詳細が必要な時に読むreferences/workflows.md — feature 開発・並列作業などの手順パターンが必要な時に読むreferences/troubleshooting.md — エラー診断・復旧手順が必要な時に読むHand the current work to another agmsg agent — write a handoff doc, send its path as one line.
Use when adding, closing, or pruning entries in a repository's `TODO.md`, when moving finished work into `CHANGELOG.md`, or when setting up local task tracking for a repository that has no tracker. Do not use for entrypoint-docs drift review (`docs-entrypoint-review`), for cutting a release version section or tag (the repository's release workflow), for manager-facing work reports (`work-log-maintenance`), or for commit splitting (`atomic-commit`).
JEY workspace 固有の Linear 運用ルール: issue のプロジェクト自動ルーティング、ラベル/タイトル/取引ログの書式、Asana からの移行マッピング、ガードレール。CRUD 自体は Linear MCP tools を使い、MCP が使えない環境や MCP に無い操作のみ GraphQL スクリプトへフォールバックする。Use when creating or editing Linear tasks, choosing a project or label, migrating task notes from Asana, or appending transaction logs (date/payment/price) to an existing issue.
Curate external agent collections into this APM workspace. Use when evaluating whether an outside agent repository can be installed through APM, importing selected agents into catalog/agents, recording provenance, or refreshing curated agents from upstream.
Select and run expert review lanes for UI, forms, design specifications, accessibility, and multi-device product quality when ordinary /review or code review is too shallow.
高級モデル(Claude Fable/Opus、Codex sol)のセッションで実装作業を受けたとき、 自分で書かずに安価な Worker モデルへ委譲する Orchestrator-Worker 運用。 Use when the user asks to implement, fix, refactor, add tests, or migrate code; when a task spans multiple files or independent subtasks that could run in parallel; or when another skill needs the delegation-vs-inline decision or the model tier mapping.