メニュー
Manage git worktrees using the gwm script. Supports creating, listing, removing, and checking status of worktrees. Use when the user says "create git worktree", "new worktree", or needs to work with multiple branches simultaneously via git worktrees.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | gwm |
| description | Manage git worktrees using the gwm script. Supports creating, listing, removing, and checking status of worktrees. Use when the user says "create git worktree", "new worktree", or needs to work with multiple branches simultaneously via git worktrees. |
| disable-model-invocation | false |
| allowed-tools | ["Bash(bash .claude/skills/gwm/scripts/gwm.sh:*)"] |
Manage git worktrees using the gwm.sh script located at skills/gwm/scripts/gwm.sh in the agent-resources repo.
The user invokes this skill as /gwm <command> [args], or by saying something like "create git worktree for KKEP-1234". Parse the command and arguments from the user's input. If the user says "create worktree" or similar without specifying a command, treat it as add.
Supported commands:
add <branch-name> [sparse-path] — Create a new worktree (optionally with sparse checkout)list — List all worktreesremove <branch-name> — Remove a worktree and optionally delete the branchstatus <branch-name> — Show dirty state, ahead/behind for a worktreeprune — Clean up stale worktree referenceshelp — Show available commandsFlags:
--plain — Human-readable output (always use this when presenting results)--no-restore — Skip dotnet restore and file copying after creating a worktreeThe script uses two directory paths, configurable via environment variables:
GWM_SRC_DIR — The main git repository (default: /d/kkep/projects/kk.erhvervsportal)GWM_WORKTREE_DIR — Where worktrees are created (default: /d/worktrees/kkep)Before running the add command, validate the branch name against the expected pattern KKEP-XYZQ where XYZQ is a four-digit number (e.g. KKEP-1234, KKEP-5678).
add command.Locate the script
skills/gwm/scripts/gwm.sh (relative to the agent-resources repo root)SRC_DIR)Run the command
bash skills/gwm/scripts/gwm.sh <command> [args]--plain for human-readable output--plain when presenting results to the userHandle the output
status: ok): present the message and relevant data to the userstatus: error): show the error message and suggest corrective actionAfter creating a worktree (successful add command)
/d/worktrees/kkep/KKEP-1234/src)cd does not persist between Bash tool calls, so do NOT try to cd into the folder — each shell invocation is independentcd <worktree-path> && or use absolute pathsExamples
bash skills/gwm/scripts/gwm.sh add KKEP-1234 --plainbash skills/gwm/scripts/gwm.sh add KKEP-1234 src/MyProject --plainbash skills/gwm/scripts/gwm.sh add KKEP-1234 --no-restore --plainbash skills/gwm/scripts/gwm.sh list --plainbash skills/gwm/scripts/gwm.sh status KKEP-1234 --plainbash skills/gwm/scripts/gwm.sh remove KKEP-1234 --plainbash skills/gwm/scripts/gwm.sh prune --plainIf no command is provided, run bash skills/gwm/scripts/gwm.sh help --plain and show the available commands.
| Error | Cause | Fix |
|---|---|---|
| "Branch already exists locally" | Branch was previously created | Use gwm status <branch> to inspect, or gwm remove <branch> first |
| "Incomplete worktree found" | Previous creation failed partway | Run gwm remove <branch> to clean up, then retry |
| "Sparse path not found" | The path doesn't exist in the repo | Check the path with git ls-tree --name-only HEAD |
| "SRC_DIR does not exist" | Env not configured for this machine | Set GWM_SRC_DIR environment variable |
| "dotnet restore failed" | Build dependencies issue | Use --no-restore to skip, then restore manually |
Update the project's CLAUDE.md with meta learnings, conventions, gotchas, and significant codebase changes. Use when the user asks to update CLAUDE.md, capture learnings, document project conventions, or reflect recent work in the project guide.
Review the current Pull Request that has been checked out locally with structured feedback on code quality, issues, testing, and suggestions. Use when you need a comprehensive code review of a PR branch.
Catch up on branch changes by reviewing all changes between current branch and master/main, analyzing key files, and providing a comprehensive summary. Use when you need to understand what changed in a feature branch.
Perform a refactor pass focused on simplicity after recent changes. Use when the user asks for a refactor/cleanup pass, simplification, or dead-code removal and expects build to verify behavior.
Analyze the specified function from the given file with detailed line-by-line breakdown. Use when you need to understand what a function does, how it works, and why it was implemented that way.
Display Claude conversation history in an easy-to-scan format showing recent sessions with dates, projects, and topics. Use when you want to review past conversations or resume a previous session.