Operations worktree
Safe git worktree creation and hygiene workflow that defaults new branches to an up-to-date remote default branch instead of local HEAD.From its SKILL.md
npx -y skills add vincentkoc/dotskills --skill operations-worktreeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.5 KB, as published. Nobody here has run it
Operations Worktree
Purpose
Create and manage worktrees safely and consistently across projects while avoiding stale branch bases.
When to use
- You need a new task branch in a new worktree.
- You are juggling many concurrent worktrees.
- You need to avoid branching from stale local
mainor localHEAD.
Workflow
- Ensure you are inside the target repository (main checkout or any linked worktree).
- Create a new worktree with the shell wrapper:
gwt new <branch>- Optional explicit base:
gwt new <branch> <start-point>
- If shell wrappers are unavailable, use raw git safely:
default=$(git symbolic-ref --quiet --short refs/remotes/origin/HEAD 2>/dev/null || echo origin/main)base=${default#origin/}git fetch origin "$base" --prunegit worktree add -b <branch> <path> "origin/$base"
- For OpenClaw PR review worktrees, prefer that repository's native PR review-init helper instead of hand-assembling refs.
Inputs
- Branch name (required)
- Optional start-point (branch/tag/commit)
- Optional destination path (for raw git mode)
Outputs
- New linked worktree checked out on the target branch.
- Default base anchored to a fetched remote default branch unless explicitly overridden.