OpenParable
Skip to content
← Back to skills

Worktree Detection

Development
worktree-detection

Worktree Detection is an Agent Skill for development published in the marmelab/atomic-crm repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

How to find a Git worktree by task number without hardcoding paths. Use in hooks or scripts that need to locate a specific task's worktree.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/marmelab/atomic-crm/blob/HEAD/.claude/skills/worktree-detection/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/worktree-detection, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Worktree Detection

Reference snippet for locating a task's Git worktree from its task number, without hardcoding paths.

When to Use

  • Inside a hook or script that must act on a specific task's worktree.
  • Any time you'd otherwise hardcode a /tmp/... worktree path.

Pattern

TASK_NUM="TASK-005"

WORKTREE=$(git worktree list --porcelain \
  | grep "^worktree " \
  | awk '{print $2}' \
  | grep -i "${TASK_NUM}" \
  | head -1)

if [ -z "$WORKTREE" ] || [ ! -d "$WORKTREE" ]; then
  echo "No worktree found for ${TASK_NUM} — skipping"
  exit 0
fi

Why this works

git worktree list reads from Git's internal registry — it knows every worktree regardless of where it was created. No assumptions about directory structure or machine-specific paths.

Extracting TASK_NUM from agent variables

TASK_NUM=$(echo "$TASK_OWNER $TASK_SUBJECT" | grep -oP 'TASK-\d+' | head -1)

Works whether the task number appears in the owner field or the subject line.

Red Flags

  • A hardcoded /tmp/... worktree path instead of querying git worktree list.
  • Assuming a directory layout rather than reading Git's registry.
  • Treating a missing worktree as an error instead of skipping cleanly (exit 0).

Verification

  • Worktree resolved via git worktree list --porcelain, never a hardcoded path.
  • A missing/absent worktree is handled (skip, don't crash).