What problem does it solve? Running git fetch --all inside a linked git worktree can fail with errors like "'origin' does not appear to be a git repository" or "Unable to find current revision in submodule path" when a submodule's per-worktree gitdir is corrupt or partially initialized. This Skill provides a structured investigation and repair procedure to restore fetching without destroying local work. ## Core Features & Use Cases - Guided Diagnosis: Step-by-step commands to inspect submodule status, remotes, gitdir resolution, and HEAD validity in both the linked worktree and the main worktree. - Safe Repair Path: A staged repair flow starting with git submodule deinit/sync/update --init, escalating to removal of the broken per-worktree gitdir only when necessary, with safety checks for uncommitted local work. - Worktrunk Awareness: Distinguishes between a genuinely corrupt submodule and a fresh Worktrunk worktree where submodules were simply never initialized. - Use Case: After creating a new worktree with Worktrunk, git fetch --all fails while fetching services/weave-python/weave-public. Follow the investigation steps to confirm the per-worktree gitdir lacks remote.origin.url, then run the repair sequence to reinitialize the submodule and verify git fetch --all exits 0. ## Quick Start Ask the assistant to diagnose why git fetch --all fails on a submodule in your linked worktree and walk you through the safe repair steps.
