lens-sandbox: Skill for Claude Code

Ship — pipeline dispatcher

You contain zero domain logic. Your only job is: figure out where the work stands, invoke the right sub-skill via the Skill tool, and keep going until the next human gate or until the pipeline is done. The sub-skills own all behavior and all human checkpoints — you inherit their pauses, you never add shortcuts around them.

One invocation does as much as the next human gate allows. Across a large effort the user runs /ship many times; each time you resume from observable state, never from conversation memory.

Arguments

• (empty) — detect phase from the current branch and plan file.
• Issue number / #124 / issue URL — read it (gh issue view <n>) and use its content as the problem seed for planning.
• Free text — a new idea; start at planning with it as the problem seed.

Isolated worktree

Do NOT run the pipeline in the user's working directory — they may be in the middle of something else, and /ship can start from a one-line idea while they sit on main. When the Spec + plan phase creates the feature branch, create a worktree for it (same pattern as /code-review):

MAIN_ROOT="$(git worktree list | head -1 | awk '{print $1}')"
SHIP_DIR="$MAIN_ROOT/.ship/<branch>"
mkdir -p "$MAIN_ROOT/.ship"
git worktree add "$SHIP_DIR" -b <branch> origin/main

Ensure .ship/ is listed in .git/info/exclude. Every subsequent phase — implementation, /green, make e2e, /code-review, /create-pr — runs inside $SHIP_DIR. On resume, if the plan file names a branch whose worktree is missing, re-add it (git worktree add "$SHIP_DIR" <branch>).

The worktree builds its own target/ — real disk on this host. /green's disk guard applies per-worktree.

Cleanup happens on PR terminal state, not at first "everything ticked" — an open PR can still receive review comments, and the Respond phase needs the worktree. When the Done row runs, check gh pr view --json state:

• MERGED or CLOSED → git worktree remove "$SHIP_DIR" (reclaims its target/), git branch -d <branch>, delete the plan file, and git worktree prune.
• OPEN → keep everything; report "awaiting review/merge — rerun /ship after merge to clean up".
• No PR / no GitHub → there is no merge event to observe; ask the user before removing anything.