herdr-sidebar: Skill for Claude Code

Feature worktree

When the user asks for a new feature, give it its own git worktree (own folder + branch) and its own Herdr pane before writing code — several agent sessions often run against this repo at once, and a shared checkout means branch switches and half-finished edits land under each other's feet. One feature = one worktree = one pane, named after the feature.

Steps

1. Already isolated? Just build. If this session's cwd is already under .claude/worktrees/, you ARE the feature pane — implement the request right here, don't nest another worktree or spawn another pane. Skip to step 5.

2. Not in Herdr? Fall back to in-place. If HERDR_ENV is not 1, there are no panes to spawn — enter the worktree in THIS session with the EnterWorktree tool (name: <slug>) and build here. Skip the pane steps.

3. Derive a short kebab-case slug from the request ("add a diff view to herdr-aa-git" → git-diff-view).

4. Spawn the feature's pane, then hand it the task. Do this from the current session; keep your own focus where it is (--no-focus everywhere).

   a. Create the worktree FIRST — before the pane exists. You are running Bash (Git Bash), so && is fine here; it is only the PowerShell panes that reject it. If the repo has an origin remote, fetch and branch from origin/main; otherwise branch from main:

   git fetch origin && git worktree add .claude/worktrees/<slug> -b <slug> origin/main
   # no origin yet:
   git worktree add .claude/worktrees/<slug> -b <slug> main
   

   Order matters: doing this first lets the pane START inside the worktree (step c), which buys two things. (1) herdr's recorded cwd for that pane is then honest — if you instead Set-Location after the shell boots, herdr keeps reporting the shell's START dir (the main checkout) forever, so every feature pane claims to be somewhere it is not. (2) No shell chaining in the pane at all — launching Claude becomes a bare command.