Files
computer-playbook/skills/i8-worktree-create/SKILL.md
kevinveenbirkenbach f6b361f42c feat(agents): add the worktree skills and the path they write to
A second branch needs its own checkout to be worked on in parallel, with its own
slot, subnet, ports and container names so two deploys do not take each other's.
The two skills route to the make targets that create and release one.

The sandbox gains the worktree directory as a writable path, without which the
checkout cannot be created and the skills are unusable. It is the only change
to the permission file: one write path, no deny or ask rule touched.
2026-08-06 21:34:05 +02:00

26 lines
1.2 KiB
Markdown

---
name: i8-worktree-create
description: >
Check a branch out into an isolated parallel worktree with its own slot,
subnet, ports and container names (make worktree-up). Trigger whenever a
second branch needs a working copy alongside the primary checkout, for
example to run two deploys at once. Infinito.Nexus specific.
---
Follow the instructions from AGENTS.md, then run
`make worktree-up branch=<branch>` (the default action of this skill). The
worktree lands under `~/.local/share/worktrees/<domain>/<account>/<repo>/<branch>`
and joins the primary checkout's cache stack instead of starting its own.
The branch MUST exist and MUST NOT be checked out anywhere else; resolve a
collision with `make worktree-prune` or `make worktree-down` first. Pass
`base=<dir>` only when the operator names a different parent directory, and
then repeat that same `base=` in every later `make worktree-down` call.
Report the slot, path, subnet, bind IP and container name from the target's
summary, and hand the operator the `cd <path>` plus `make compose-up` follow-up.
Begin by clarifying every open requirement with the `active-listening` skill,
then work under the `robot` skill. The task is finished only when the worktree
exists and its `.env` has been generated.