.github/skills/speckit-worktree-create/SKILL.md
Spawn an isolated git worktree for a new or existing feature branch
npx skillsauth add pradeepmouli/lspeasy speckit-worktree-createInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Spawn an isolated git worktree for a feature branch so you can work on multiple features in parallel without switching branches. Each worktree gets its own directory with a full working copy.
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty). The user may specify a branch name (e.g., "003-user-auth") or "current" to create a worktree for the current branch.
.specify/ directoryDetermine target branch: Identify which feature branch to create a worktree for:
Choose worktree location: Determine the worktree directory path:
.worktrees/{branch-name}/ relative to the repository root.worktrees/ directory does not exist, create it.worktrees/ to .gitignore if not already presentCreate the worktree: Execute the git worktree command:
git worktree add .worktrees/{branch-name} {branch-name}git worktree add .worktrees/{branch-name} -b {branch-name} origin/{branch-name}Verify spec artifacts: Check that the worktree has access to spec artifacts:
specs/{branch-name}/ directory exists in the worktreeReport: Output a summary:
# Worktree Created
| Field | Value |
|-------|-------|
| **Branch** | {branch-name} |
| **Worktree path** | .worktrees/{branch-name}/ |
| **Spec artifacts** | spec.md ✅, plan.md ✅, tasks.md ❌ |
## Next Steps
- `cd .worktrees/{branch-name}/` to work in the isolated worktree
- Run `/speckit.implement` inside the worktree to build the feature
- Run `/speckit.worktree.list` to see all active worktrees
- When done, run `/speckit.worktree.clean` to remove the worktree
.worktrees/ only.worktrees/ is ignored to prevent accidental commitstools
Use for ANY rename, file-move, or move-symbol refactor — especially rename-heavy work across multiple files. Claude Code's built-in LSP tool is READ-ONLY (find references, but no rename / file-move / move-symbol). Hand-editing those refactors silently misses re-exports, aliased imports, type-only imports, and {@link} doc references. This skill drives a real language server via the `lspeasy` CLI to apply a correct WorkspaceEdit that catches every reference. Trigger when the user asks to rename a function/class/variable/type project-wide, move a file and fix its importers, or pull a symbol out into another module.
tools
Documentation site for lspeasy Use when: You are building a browser-based LSP client, a WebSocket-backed language....
tools
Documentation site for lspeasy Use when: You are implementing a custom client layer and need the same validation....
tools
Use when working with lspeasy (client, core, server). Covers: lsp, language-server-protocol, lsp-client, language-client, jsonrpc, transport, lsp-server, language-server.