← ClaudeAtlas

initlisted

Configure optional per-project Git worktree settings through guided questions and validated .worktree.json writes.
sebastiansulinski/claude-plugins · ★ 0 · Code & Development · score 62
Install: claude install-skill sebastiansulinski/claude-plugins
# Configure worktrees Use this workflow when the user asks to create or change worktree settings. Configuration is optional. Resolve the bundled [worktree runtime](../../scripts/worktree.sh) relative to this skill file and assign its absolute path to `worktree_runtime`. Run from the owning repository, including inside a targeted submodule. 1. Read applicable repository instructions. Run `bash "$worktree_runtime" config` and inspect the existing `.worktree.json` if present. The command shows resolved settings, while the file identifies explicit overrides. Retain existing keys and values unless the user requests changes. 2. Inspect available branches and `origin/HEAD`, plus the presence of `composer.json`, `package.json`, `.env`, and a committed `.worktree-setup.sh`. Ground recommendations in these observations. 3. Gather only the settings still needed, using an available input tool within its question limit or ordinary conversation. Treat existing values and explicit instructions as the defaults: - Base branch for new worktrees. - Destination, outside both the repository and any superproject. The normal destination is a sibling of the repository, or a sibling of its superproject for submodules. - Branch prefix. Preserve an existing prefix; for a new Codex configuration recommend `codex/` unless project instructions say otherwise. The unchanged shared engine uses `wt/` without configuration. - Bootstrap: copy `.env`, run `composer install`, a