What problem does it solve? Parallel feature work in git normally collides on shared resources: the same .test domain, Redis keys, sessions, queue jobs, and database. This Skill manages parallel git worktrees so each checkout gets its own isolated environment — a unique Herd URL with TLS, an isolated .env (APP_URL, REDIS_PREFIX), and optionally a cloned MySQL database — without ever switching the parent checkout. ## Core Features & Use Cases - Create: Branch a new worktree off origin/<base> with runtime-dir cloning (vendor, node_modules) via APFS copy-on-write, Herd link + TLS for Laravel repos, and smoke-test verification. Non-Laravel repos get a plain git worktree automatically. - Destroy: Dry-run teardown scope with content-aware merge checks against both base and main, then gated teardown that unlinks Herd, drops only the clone DB, flushes prefixed Redis keys, and deletes merged branches. - List & Sync: Report all worktrees with link/cert status, merge state, and ahead/behind counts; rebase or merge a worktree onto a ref without pushing. - Use Case: Ask for two worktrees for two bugfixes and receive two paths, each with its own https://<repo><id>.test URL and isolated Redis prefix, ready to cd into. ## Quick Start Ask the agent to create a worktree for your current feature, for example: create a worktree for the login fix and give me the path and URL.