worktree-from-issue

To create a git worktree for a GitHub issue, this Skill parses the issue number and description to generate a branch name, verifies the issue exists, and establishes an isolated worktree with the new branch. It sets up the development environment within that worktree automatically.

Automating branch naming from GitHub issues is done by parsing the issue number and description to generate a branch name following a specified convention, such as `fix/3562-bug-description`. This ensures consistent naming across your development workflow without manual input.

A git worktree setup helps issue tracking by establishing an isolated development environment for a specific issue, preventing interference with the main codebase. This allows you to implement fixes or features cleanly while the main branch remains untouched.

Yes, you can verify GitHub issue existence before creating a new branch. The Skill checks the issue validity on GitHub as part of its workflow, ensuring the branch and worktree are only generated for documented issues.

You do not need a specific branching convention to use a git worktree for issue implementation, but the Skill generates a branch name based on a predefined convention derived from issue details. It automatically structures the branch name using the parsed issue number and description.

Using a git worktree instead of branching directly in the main repository provides an isolated worktree for the new branch, preventing interference with the main codebase. It configures a dedicated development environment for addressing specific GitHub issues cleanly.