Safe Git Worktrees for Parallel Coding

“I need to fix production, but my feature branch is halfway done.” Create a separate working directory without stashing or disturbing the current checkout. This workflow catches occupied branches, ambiguous starting points, shared runtime resources, and unfinished work before they become collisions or lost changes.

What it does

• Maps existing worktrees to their paths, branches, and current commits before creating another checkout.
• Creates a new task branch from an explicit base commit, or safely attaches an existing available branch.
• Verifies the new checkout's branch, commit, clean state, and shared Git object store.
• Identifies dependencies, environment files, ports, databases, and caches that Git worktrees do not isolate.
• Produces a concise handoff with the exact working directory, branch, base, and validation results.
• Removes completed worktrees after checking local files and commit preservation, with recovery steps for moved or missing directories.

What you get

An appropriately sized command sequence or completed setup with a verified handoff. Cleanup requests include a preservation check and readback of the remaining worktrees; commands that have not been executed are labeled clearly.

Best for

Developers running multiple Claude Code sessions, maintaining a feature while handling a hotfix, or comparing branches in separate working directories.