Baseline
Skill rock3r/pioneer/.agents/skills/using-git-worktree/evals/baseline
Create and verify an isolated pioneer Git worktree. Use before feature implementation on the default branch or whenever the user requests worktree isolation.From its SKILL.md
npx -y skills add rock3r/pioneer --skill baselineAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.7 KB, as published. Nobody here has run it
Using Git worktrees
Preflight
- Check whether
git rev-parse --git-common-dirdiffers fromgit rev-parse --git-dir. If so, the session is already in a worktree; report it and stop. - Check the current branch. If it is a non-default feature branch, report that isolation already exists and stop unless the user explicitly requests another worktree.
- Confirm the repository has at least one commit. An unborn branch cannot seed a normal feature worktree.
- Use
.worktrees/<branch-name>and verify.worktrees/is ignored withgit check-ignorebefore creation.
Create
- Fetch the selected base only when the user has authorized network access.
- Choose a short hyphenated branch name tied to the task.
- Create the branch and worktree explicitly:
git worktree add .worktrees/<branch-name> -b <branch-name> <base-branch>
- Run all subsequent commands with the worktree as the working directory or with explicit absolute paths.
- Install exact dependencies with
npm ci. - Run
npm run checkto establish a clean baseline.
If the baseline fails, report the failure and ask whether to investigate or proceed. Do not blur pre-existing failures with task changes.
Report
Return the absolute worktree path, branch, base revision, dependency-install result, and validation result.
Cleanup
Clean up only after the branch is merged or the user explicitly abandons it. Run cleanup from the main checkout, inspect worktree status first, and never force-remove a worktree containing changes without explicit approval.