Using git worktrees
Skill kimtth/agent-skill-100-lines-or-less/skills/using-git-worktrees
🧿 Minimal but effective AI agent skill definitions in 100 lines or less.
npx -y skills add kimtth/agent-skill-100-lines-or-less --skill using-git-worktreesAssembled 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.
- 2 stars2 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.
What its author says it does
Copied from the file, not written here
Use when: starting feature work that should be isolated from the current checkout or branch.
SKILL.md
1.1 KB, 221 tokens by cl100k_base, as published. Nobody here has run it
Goal: create or detect an isolated workspace without fighting the user's tooling.
Workflow:
- Detect whether the repo is already in a worktree.
- Guard against mistaking submodules for worktrees.
- Ask before creating a new worktree unless instructions already allow it.
- Prefer platform-native worktree tools when available.
- Fall back to
git worktree addonly when no native tool exists. - Run project setup in the isolated workspace.
- Record branch, path, and cleanup expectations.
Checks:
git rev-parse --git-dir
git rev-parse --git-common-dir
git branch --show-current
git rev-parse --show-superproject-working-tree
Use for:
- risky feature work
- parallel implementation branches
- executing plans while preserving the user's current checkout
Rules:
- do not create nested or duplicate worktrees
- do not switch the user's current branch as a shortcut
- do not delete a worktree until changes are integrated or abandoned by request
- explain detached HEAD limitations before finishing