git-workflow calls itself a router but named two of the six domains it routes to; the other four appeared nowhere in the file. All six are now named, with a routing table in the always-loaded body. git-submodules lost the foreach shell-variable semantics -- only the bare names survived, though $sm_path and $displaypath differ solely by which directory you are in. The table is back. Its relocated commands had also dropped the rtk git prefix its own SKILL.md mandates; 24 of them are re-prefixed. The wider rtk inconsistency across the plugin stays with #113. Also restores git-commits' body and footers output fields, git-branches' tag/ branch detection commands, git-worktrees' git config --worktree, pc-run's ambiguity fallback, git-remotes' git-history boundary, and git-history's pickaxe triggers. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EJJrm5YmacbwMdzZpXcoti
git-worktrees
Manage git worktrees to enable multi-branch parallel development across isolated directories.
What it does
This skill handles worktree operations within the git workflow suite. It creates, lists, locks/unlocks, moves, removes, prunes, and repairs worktrees — letting an agent work on multiple branches simultaneously without stashing. It returns structured results (paths, branches, lock status) suitable for agent composition. For multi-step flows spanning branch strategy plus worktree setup, git-workflow handles the broader orchestration and delegates the worktree mechanics here.
Usage
/git-worktrees
Describe your worktree task: create a worktree for a branch, list existing worktrees, lock one for removable media, move, remove, prune, or repair. The skill will handle the operation with appropriate safety checks and return results.
Files
| File | Purpose |
|---|---|
SKILL.md |
Dispatch table, per-operation gates, and the report format |
references/README.md |
Describes the references directory contents |
references/worktrees.md |
Read when an operation needs more than the dispatch table: shared vs. per-worktree state, the add command forms, the full add flag table, orphan branches, sparse-checkout, removable-media locking, remote disambiguation, where to run repair from, config keys, and the emergency-fix and PR-review patterns |
references/sources.md |
Research sources and provenance |