add-worktree

To create a Git worktree for a GitHub issue, the Skill reads the issue, validates it is open, and automatically generates an isolated local checkout directory with a consistently named branch for implementation work.

Branch naming for a worktree is determined by detecting branch-type prefixes from the GitHub issue's labels or keywords, ensuring consistent naming conventions while checking for existing branches to prevent duplication.

Yes, you can copy repository-specific configuration into a new Git worktree. The Skill optionally duplicates your existing .hachimoku configuration into the new directory to preserve custom agent and review settings.

If a branch or worktree already exists for an issue, the Skill performs safety checks before creating anything. It validates existing branches and local checkout directories to prevent duplicate worktree creation and avoid overwriting files.

No, you do not need to manually check if a GitHub issue is open. The Skill handles issue lookup internally and validates that the issue is open before initiating the branch and worktree creation process.

The best way to isolate development work is using a Git worktree. This approach creates a dedicated local checkout directory and branch for the issue, preventing disturbances to your main project workspace during implementation.