{"id":"7c9b9b4b-acfb-45a7-b59e-5aab589c0a84","shortId":"beBASN","kind":"skill","title":"fast-worktree-reuse-with-head-pointer-checks","tagline":"Resume existing worktrees quickly by checking stored HEAD pointers before fetching or recreating.","description":"# SKILL: Fast Worktree Reuse With Head Pointer Checks\n**Domain:** git-worktree\n**Trigger:** Apply when the user asks to enter or resume a named worktree and you want to avoid redundant `git fetch`/`git worktree add` calls if the worktree already exists.\n**Source Pattern:** Distilled from reviewed permission, shell-safety, and worktree-management implementations.\n\n## Core Method\nBefore reaching for `git worktree add`, compute the worktree path and read its git head pointer directly (no subprocess). If the file exists and contains a SHA, treat the worktree as already created: return the path/branch, skip fetch, and let the CLI proceed immediately. Only when the HEAD file is missing do you fetch and `git worktree add`, knowing the directory is missing or corrupted.\n\n## Key Rules\n- Read claude worktrees