worktree-detection

To find a specific Git worktree path by task number, match a task identifier like TASK-005 against the output of git worktree list. The detection snippet parses the porcelain output, selects the first matching directory, and validates that it exists.

When no matching Git worktree is found, the detection script exits cleanly with a skip message instead of failing. This prevents automated CI hooks and agent-driven workflows from crashing when a specific task worktree does not exist.

Yes, you can extract a task number from agent variables like TASK_OWNER and TASK_SUBJECT. The detection logic uses a TASK-\d+ pattern to derive the task number, allowing it to locate the correct worktree across varying agent variable formats.

The best way to avoid hardcoded paths in per-task worktree scripts is to dynamically discover the directory by matching a task identifier against git worktree list output. This approach validates the selected path before executing operations.

Yes, worktree path discovery works with CI hooks and agent-driven development workflows. It is specifically designed to parse git worktree list output, select the first matching directory, and gracefully skip execution if no match is found.