Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →gmickel/flow-next-worktree-kit
Manage git worktrees (create/list/switch/cleanup) and copy .env files.
Passed 16 of 20 test cases with the skill, and 8 of 20 without it.
and 6 more in the full report
9 fixed9 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to inspect all active git worktrees currently managed in my project using the helper script. Which command should I run?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends bash "${CODEX_HOME:-$HOME/.codex}/scripts/worktree.sh" list to display registered worktrees. | Missed | Passed |
The instructions your model reads when the skill loads.
Use the manager script for all worktree actions.
bash "${CODEX_HOME:-$HOME/.codex}/scripts/worktree.sh" <command> [args]
Commands:
create <name> [base]listswitch <name> (prints the worktree path; it cannot change your shell's directory - use cd "$(... switch <name>)")cleanup [<name>...] [--yes] (no args = interactive; names skip the prompt; --yes skips the confirmation, required off a terminal)copy-env <name>Safety notes:
create does not change the current branchcreate sets no upstream on the new branch (--no-track) - under the upstream-based push modes (simple, upstream, current) a bare git push cannot aim at the base branch; under the default push.default=simple (without push.autoSetupRemote) the first push needs git push -u origin <name> (legacy push.default=matching pushes all name-matched branches regardless of upstream)cleanup does not force-remove worktrees and does not delete branchescleanup deletes the worktree directory (including ignored files); removal fails if the worktree is not clean.env* is copied with no overwrite (symlinks skipped).worktrees/ or any worktree path component is a symlinkcopy-env only targets registered worktreesorigin fetch is optional; local base refs are allowedorigin only when base looks like a branch.worktrees/create initializes .worktrees/.gitignore (* plus !.gitignore) when
absent, so git add -A cannot stage nested worktrees as gitlinks; existing
custom ignore files are preservedtest cases passed, vs 8 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.