worktrees
/worktrees
Tworzy, sprawdza, naprawia i usuwa worktree gita, uzupełniając brakujące zależności, hooki i pliki ignorowane, na przykład .env.
- Autor
- chewygumxx ↗
- Repozytorium
- agent-library ↗
- Licencja
- GPL-3.0
- Ostatnia zmiana repozytorium
- 13.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 1
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
GPL-3.0, otwarta.
- SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.
Co robi i kiedy
Tworzy, sprawdza, naprawia i usuwa worktree gita, uzupełniając brakujące zależności, hooki i pliki ignorowane, na przykład .env.
Oryginalny opis (EN)
Use when creating, entering, checking, repairing or removing a git worktree, or when a worktree lacks dependencies, git hooks, skills or ignored files such as .env that the main checkout has.
Jak działa
- Making one
- What sets one up
- Checking one
- Repairing one
- What differs in a worktree
- Probing
- Removing one
Podgląd SKILL.md
--- name: worktrees description: >- Use when creating, entering, checking, repairing or removing a git worktree, or when a worktree lacks dependencies, git hooks, skills or ignored files such as .env that the main checkout has. license: GPL-3.0-only --- <!-- - - ~chewygumxx/agent-library.git - ::: :/skills/worktrees/SKILL.md - --> # Worktrees A new worktree holds only what git tracks. Everything else the main checkout has, the dependencies, git hooks, linked skills and ignored files, is missing until something brings it. Here is how a worktree is made so that it comes out whole, then checked, repaired and removed. ## Making one Take the first of these that applies: 1. The repository's instructions name a tool or a place: use it. They win over any general skill that says otherwise, such as one that makes a `.worktrees/` directory. 2. The repository configures a tool, as `.config/wt.toml` does worktrunk: use that tool. 3. The user's own tooling is at hand, such as worktrunk's `wt switch --create <branch>`, your client's worktree or your multiplexer's: use it. Where such a tool puts worktrees is its own setting; leave the path to it. 4. None of these: run `git worktree add` at a path the user gives or agrees to. For a subagent, make its worktree first and name the path in its prompt, such as with `wt switch --create <branch> --no-cd`. Claude Code's Agent tool with `isolation: "worktree"` makes a throwaway `agent-<id>` branch instead, for work you do not mean to keep on a named branch. ## What sets one up Find what the repository declares, as a worktree made by any tool then comes out whole: - A `post-checkout` hook, such as `.husky/post-checkout`: git runs it in a new worktree with the null commit as its first argument, so it can install dependencies, which also brings back the git hooks and skills that install links. - `.worktreeinclude`, gitignore patterns of ignored files for Claude Code to copy from the main checkout. Worktrunk reads it too, under `wt step copy-ignored --require-include`. - Worktrunk's hooks, in `.config/wt.toml` and `~/.config/worktrunk/config.toml`, which run only for its own commands and the clients it serves. Where none of these covers something the main checkout has, the worktree goes without it until you bring it by hand. Say so to the user: a hook or an include line would fix it for every worktree after this one. ## Checking one Compare it with the main checkout, as the checks that matter depend on the repository: - Dependencies are installed: `node_modules`, a Python environment or the like. - Git hooks run: git shares `.git/hooks` across worktrees, but a hooks directory generated by install, such as `.husky/_`, is per worktree. Without it, nothing is linted at commit. - `ls .claude/skills .agents/skills` lists what the main checkout's do. - The repository's own test command passes. ## Repairing one From inside the worktree, run the repository's install command, then whichever copy applies, such as `wt step copy-ignored --require-include`, which copies from the main checkout whichever branch it is on. ## What differs in a worktree - Ignored files, such as a `settings.local.json`, are the worktree's own. The user's permissions in the main checkout's file do not come with it unless it is copied. - Anything keyed on the checkout's path, such as a client's memory or history, may treat the worktree as another project. ## Probing To try a hook or a copy, add a throwaway worktree in a scratch directory with `git worktree add`, not `wt switch`, whose user hooks may have side effects, such as opening a pane. Remove it with `git worktree remove`; `--force` only on a probe whose changes are your own. ## Removing one Once the branch is merged or abandoned, remove the worktree with the tool that made it, such as `wt remove <branch>`, or `wt merge` when merging locally; `git worktree remove` for one git made. Look for uncommitted work first, as a forced removal destroys it.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · chewygumxx/agent-library | 90 | GPL-3.0 |
| ericrisco/rsc-harness | 100 | MIT |
| tony/skills | 100 | MIT |
| srstomp/pokayokay | 90 | MIT |
| diegoperezg7/ramify | 86 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 29a675b5feab (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100worktree
Tworzy i usuwa worktree gita do równoległej pracy, kopiuje ignorowane pliki i env oraz uruchamia konfigurację po utworzeniu. - 100worktree
Tworzy worktree gita dla nowej gałęzi funkcji i przygotowuje w nim pliki oraz zależności. - 96flow-next-worktree-kit
Zarządza drzewami roboczymi git: tworzy je, przełącza i porządkuje, a także kopiuje pliki .env. - 96flow-next-worktree-kit
Zarządza drzewami roboczymi git: tworzy je, przełącza i porządkuje, a także kopiuje pliki .env. - 100worktree
Uruchamia, sprawdza i czyści worktree git dla sesji, pilnując zasady jedna sesja, jeden worktree i jedna gałąź. - 100setting-up-worktree-hooks
Tworzy idempotentny skrypt przygotowania worktree w repozytorium: pliki env, instalację zależności i kroki budowania, wywoływany z hooków wt.toml i orca.yaml.