worktree-setup
SolidSet up worktree-plus for a repo — manage git config (baseBranch, branchPrefix, dirBase, guessRemote) and build the .worktreeinclude / .worktreelink files by scanning which gitignored files actually exist. Use when the user asks to set up or configure worktree-plus, view or change worktree settings, reset the plugin config, or decide which gitignored files should be copied or symlinked into new worktrees.
Install
Quality Score: 84/100
Skill Content
Details
- Author
- LeeJuOh
- Repository
- LeeJuOh/claude-code-zero
- Created
- 6 months ago
- Last Updated
- 1 weeks ago
- Language
- JavaScript
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
worktree-setup
Provision a freshly-created git worktree so it's actually ready to work in — trust its mise.toml, copy gitignored-but-needed files (Rails config/master.key, .env, …) from the main checkout, and re-mark shebang scripts executable. Use right after creating a worktree (native EnterWorktree or `git worktree add`), or when a new worktree errors with "mise.toml not trusted", is missing secrets/.env, can't load the app, or has non-executable scripts. Also when parallel worktrees collide on the same dev-server port or database — opt into per-worktree ports + databases via a `.worktree-isolate.conf`. Pairs with using-git-worktrees (which creates the worktree; this provisions it).
worktree-new
Git worktree conventions for isolated parallel feature work. Use when starting a new coding task, feature, bugfix, or PR-review in a git repository — anytime work should get its own branch and worktree instead of touching the main checkout, or when the user asks to work in / create / list / remove a worktree. Applies to whatever repository Claude is currently in.
worktree
Creates git worktrees for isolated development. Use when user wants to "create a worktree", "start a new feature branch", "work on a fix in isolation", or needs a parallel development environment.