Agent skill
worktree-start
Create a git worktree for isolated parallel feature development. Lighter than fork-project — shares git history but zero .git contention between agents. Use when the user wants to start a feature in its own isolated workspace with separate agent sessions.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/worktree-start
SKILL.md
Worktree Start
Creates a lightweight isolated workspace using git worktree. Ideal for running 4-5 features in parallel, each managed by an independent agent session, without the disk overhead of a full clone.
What it does
- Guards
.worktrees/is in.gitignore(adds and commits if missing) - Creates a worktree at
.worktrees/<feature-name>on branchwork/<feature-name> - Installs dependencies (auto-detects pnpm / yarn / npm / cargo / pip)
- Runs a baseline check to confirm the clean starting state
- Reports the path and next steps
Usage
/worktree-start <feature-name>
How to execute
bash .claude/skills/worktree-start/scripts/worktree-start.sh "<feature-name>"
Important
- Worktrees live inside the project at
.worktrees/<feature-name>— no sibling directories - Each worktree has its own index file (no git contention between parallel agents)
- Branch naming follows the same convention as
fork-project:work/<feature-name> - The
.worktrees/dir is gitignored so worktree contents are never tracked - Always inform the user of the full path so they can open their agent session there
- Pairs with
/worktree-finishto merge back and clean up
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?