worktree-detection

To locate a Git worktree by task ID without hardcoded paths, this skill queries Git's internal worktree registry to dynamically resolve valid worktree directories using task identifiers.

Git hook scripts fail across different machines because hardcoded worktree paths break when directories move. Querying Git's internal worktree registry dynamically resolves paths based on task identifiers instead of fixed locations.

Mapping agent task identifiers to local worktree directories involves extracting task numbers from agent variables and querying Git's worktree registry to resolve the associated directory paths for automation workflows.

When locating a missing Git worktree, the script handles the absence gracefully to prevent crashes, ensuring automation workflows continue executing without failing due to unresolvable task paths.

Yes, you can use this worktree path resolution for CI/CD linting hooks. It reliably finds the correct task-specific worktree directory regardless of where it was created on the system.

The best way to resolve task-specific Git worktree paths in agent tools is querying Git's internal registry rather than relying on fixed directory structures, preventing cross-machine automation failures.