worktree-workflow

Git worktrees allow you to maintain multiple working directories from a single repository. This workflow creates a dedicated worktree for each task, preventing cross-task contamination and compartmentalizing changes to keep your branch history clean and isolated.

You can automate worktree creation by running the start-task-worktree.sh script with a descriptive task name. This script creates a fresh task-scoped worktree and automatically initializes submodules to preserve the complete repository state for that task.

Yes, this workflow enforces commit-after-changes behavior to ensure regular, traceable commits across tasks. It automatically pushes the branch to origin after each meaningful chunk of work, keeping your remote repository history consistent and up to date.

The best way to manage branch naming is to enforce a predictable convention like task/<safe-name> across all local worktrees. This workflow provides guardrails against common misconfigurations and maintains a reusable base branch workflow for consistent tracking.

Yes, using a worktree-per-task workflow isolates your changes in a separate directory without disrupting your main Git branch. It starts a fresh worktree from a reusable base branch, keeping your primary working directory clean and focused.