Create a git worktree with isolated configuration for parallel development
Creates an isolated git worktree for parallel development with unique ports and configuration.
/plugin marketplace add eduardoarantes/claude-code-plugin-marketplace/plugin install git-simple@code-plugin-marketplacebranch-nameclaude-sonnet-4-5-20250929Create a new git worktree in the trees/ directory with completely isolated configuration for parallel execution. This enables running multiple instances of the observability system simultaneously without port conflicts, database collisions, or hook misconfiguration.
PROJECT_CWD: . (current working directory - the main project root)
BRANCH_NAME: $1 (required)
PORT_OFFSET: $2 (optional, defaults to auto-calculated based on existing worktrees, starts at 1)
WORKTREE_BASE_DIR: trees/
WORKTREE_DIR: trees/<BRANCH_NAME>
mkdir -p treesgit branch --list <BRANCH_NAME>
git worktree add trees/<BRANCH_NAME> <BRANCH_NAME>
git worktree list | grep trees/<BRANCH_NAME>cp <PROJECT_CWD>/.env <WORKTREE_DIR>/.envcp <PROJECT_CWD>/.env.sample <WORKTREE_DIR>/.envgit worktree listFollow the Report section format below to provide comprehensive setup information.
After successful worktree creation, validation, provide a detailed report in the following format:
ā
Git Worktree Created and Started Successfully!
š Worktree Details:
Location: trees/<BRANCH_NAME>
Branch: <BRANCH_NAME>
āļø Environment Files:
ā Root .env (WORKTREE_DIR/.env with API keys)
š Important Notes:
⢠This worktree is completely isolated from the main codebase
⢠You can run multiple worktrees simultaneously with different ports
š To Restart This Worktree Later:
cd trees/<BRANCH_NAME>
šļø To Remove This Worktree:
# Then remove the worktree:
git worktree remove trees/<BRANCH_NAME>
# Or force remove if needed:
git worktree remove trees/<BRANCH_NAME> --force
š Next Steps:
2. Open Claude Code in this worktree directory
3. Run commands - events will stream to this isolated instance
4. Compare side-by-side with other worktrees or main codebase
5. Each instance maintains its own database and event history
If any validation steps failed or warnings occurred, include an additional section:
ā ļø Warnings / Action Required:
- <List any warnings or actions the user needs to take>