What happens if I try to run a command in the main repository branch?

The skill includes a critical validation step that identifies when the repository name and worktree name match, flagging it as the main worktree and preventing accidental operations.

How does this skill detect my current worktree?

The skill parses your current working directory (PWD) based on the standard /workspace/repos/ / path convention used in many containerized development environments.

Will it work if I am deep inside a project's source folder?

Yes, the logic is designed to handle deeply nested paths. It extracts the primary repo and worktree segments while ignoring any subdirectories below the worktree level.

Can I still manually specify a worktree name?

Yes. The implementation pattern prioritizes explicit positional arguments or flags, only invoking the auto-detection logic as a fallback when arguments are missing.

Git Worktree Path Auto-Detection

Name: Git Worktree Path Auto-Detection
Author: manifoldlogic

bymanifoldlogic

0•

Productivity & Workflow

Automatically identifies Git repositories and worktree names based on the current directory path convention.

This skill enables Claude to automatically determine the correct Git repository and worktree names by parsing the user's current working directory. Specifically designed for environments using the /workspace/repos/<repo>/<worktree> convention, it eliminates the friction of manually providing arguments during worktree operations like merging, spawning, or cleaning up. It features robust validation to prevent accidental operations on the main repository branch and maintains accuracy even when the user is deep within nested subdirectories.

Key Features

01Graceful error handling for paths outside the workspace convention

02Smart validation to prevent destructive operations on the main worktree

03Automatic extraction of repository and worktree identifiers from PWD

04Support for deeply nested subdirectories within feature worktrees

050 GitHub stars

06Seamless fallback logic for explicit command-line overrides

Use Cases

01Automating context-aware operations within devcontainer environments

02Simplifying multi-repo management by inferring targets from current location

03Running worktree lifecycle scripts without typing repetitive arguments

Key Features

01Graceful error handling for paths outside the workspace convention

02Smart validation to prevent destructive operations on the main worktree

03Automatic extraction of repository and worktree identifiers from PWD

04Support for deeply nested subdirectories within feature worktrees

050 GitHub stars

06Seamless fallback logic for explicit command-line overrides

Use Cases

01Automating context-aware operations within devcontainer environments

02Simplifying multi-repo management by inferring targets from current location

03Running worktree lifecycle scripts without typing repetitive arguments