create-worktree
This skill contains shell command directives (!`command`) that may execute system commands. Review carefully before installing.
create-worktree
Invocation input
$ARGUMENTS below means the arguments supplied with the user's explicit invocation. In inherited Context blocks, run each ! command to collect the named value; those expressions are not expanded automatically in a skill.
Context
- Current branch: !
git branch --show-current - Current git status: !
git status --short - Existing worktrees: !
git worktree list - Recent commits: !
git log --oneline -10
Your task
Create or resume a worktree for the work at hand and continue in it. $ARGUMENTS may include a Baseline Pointer: an exact branch and full commit SHA that the caller already verified against its ticket.
Name. A Planning Baseline branch is the exact <name>; never derive a replacement. Otherwise derive <name> from what $ARGUMENTS describes — treat it as a description of the work, not as a literal name, unless it already reads like a slug. Without one, derive it from the task this session is about to start: what the user just asked for, the plan under discussion, or the uncommitted changes in Context. Keep <name> short, ASCII, and valid as a branch name (git check-ref-format --branch <name>), e.g. feat/create-worktree-command, fix/null-deref. If neither the arguments nor the session says what the work is, ask the user one short question.