From worktree
Create git worktrees using CrewChief CLI with VS Code workspace integration.
npx claudepluginhub manifoldlogic/claude-code-plugins --plugin worktreeThis skill uses the workspace's default tool permissions.
**Last Updated:** 2026-03-15
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.
Last Updated: 2026-03-15
The worktree-spawn skill orchestrates worktree creation by combining two operations:
crewchief worktree create)workspace-folder.shCRITICAL: Use the user's exact input as the worktree name.
When a user asks to create a worktree with a specific name:
Examples of correct behavior:
| User says | Worktree name | Branch name | Folder name |
|---|---|---|---|
| "create worktree PANE-001" | PANE-001 | PANE-001 | PANE-001 |
| "worktree for UIT-9819" | UIT-9819 | UIT-9819 | UIT-9819 |
| "create worktree my-feature" | my-feature | my-feature | my-feature |
| "worktree called bugfix-auth" | bugfix-auth | bugfix-auth | bugfix-auth |
The only transformation applied is validation: names must match [a-zA-Z0-9_-]+ and cannot start with a hyphen.
/workspace/repos directorycrewchief worktree command) installed# Check CrewChief CLI
command -v crewchief
# Verify workspace-folder.sh script
ls ~/.devcontainer/scripts/workspace-folder.sh
crewchief worktree create <worktree-name> --repo <repository> --branch <base-branch>
After creating the worktree, add it to the workspace file:
workspace-folder.sh add repos/<repo>/<worktree> --name "<repo> (<worktree>)"
# 1. Create worktree from main branch
crewchief worktree create feature-auth --repo crewchief --branch main
# 2. Add to VS Code workspace
workspace-folder.sh add repos/crewchief/feature-auth --name "crewchief (feature-auth)"
crewchief worktree create feature-auth --repo crewchief --branch main
workspace-folder.sh add repos/crewchief/feature-auth --name "crewchief (feature-auth)"
Use case: Standard workflow for starting new feature development. Creates the worktree from main branch and adds it to your workspace file for easy navigation in VS Code.
crewchief worktree create bugfix-login --repo crewchief --branch develop
workspace-folder.sh add repos/crewchief/bugfix-login --name "crewchief (bugfix-login)"
Use case: Working on a bugfix that needs to branch from develop instead of main.
crewchief worktree create quick-test --repo crewchief --branch main
Use case: Quickly create a worktree for temporary testing or experimentation without modifying the workspace file.
When working with the SDD (Spec-Driven Development) plugin, use worktree names that match ticket IDs for traceability:
# Start work on ticket MAPR-0001
crewchief worktree create MAPR-0001 --repo crewchief --branch main
workspace-folder.sh add repos/crewchief/MAPR-0001 --name "crewchief (MAPR-0001)"
Benefits:
Tip: The SDD plugin's do-task and do-all-tasks commands may suggest creating worktrees with ticket IDs automatically.
For worktree lifecycle management (merging, cleaning up) after creation, see the worktree-management skill.