worktree-location

What problem does it solve?

This Skill prevents CI, isolation, and path-mismatch problems caused by creating Git worktrees in inconsistent locations, especially when parallel agents or subagents are involved.

Core Features & Use Cases

• Siblings-only worktree placement: Always create worktrees as siblings of the original repository directory to keep paths stable and predictable.
• Subagent isolation guidance: Avoid using packaged subagent({ worktree: true }) when sibling placement is required; instead create the sibling worktree manually and run with cwd set correctly.
• Consistent naming for branches and worktrees: Derive worktree paths from Conventional Commit types and issue-title slugs to make automation handoffs reliable.

Quick Start

Create a git worktree using the worktree-location rules so the new checkout is a sibling of the original design-system repo and never placed under /tmp.