bk-worktree

To create an isolated git worktree, you specify a feature name, a base branch, and a task reference. This generates a separate, clean directory environment for parallel development without interfering with your main branch.

Managing parallel development tasks without conflicts requires isolated git worktrees. This approach creates separate working directories linked to the same repository, keeping your main environment stable while you develop new features or fix bugs independently.

You need an isolated git worktree when starting a complex feature that requires a clean environment. It allows you to work on multiple tasks simultaneously without switching branches or risking instability in your main development area.

After creating a git worktree with a specified feature name, you run the included environment initialization and context recording workflows. This sets up your isolated workspace and logs the task reference to maintain development context.

Yes, the bk-worktree skill includes dedicated cleanup workflows. Once your parallel development or feature isolation tasks are complete, these workflows manage the removal of the isolated git worktree to keep your workspace clean.

Yes, you can specify a base branch and a task reference when creating a new git worktree. This ensures the isolated environment branches directly from the correct version control point and links to your specific development task.