create-worktree-from-issue

Create a git worktree, branch, and tmux window for a GitHub issue.

2|1|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/cboone/cboone-cc-plugins --skill create-worktree-from-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-worktree-from-issue
Source: https://github.com/cboone/cboone-cc-plugins/tree/main/plugins/create-worktree-from-issue/skills/create-worktree-from-issue
Command: npx skills add https://github.com/cboone/cboone-cc-plugins --skill create-worktree-from-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of starting work on a GitHub issue by automatically creating a dedicated git worktree, branch, and tmux window, pre-populated with the issue's context.

Core Features & Use Cases

  • Issue-to-Worktree Mapping: Seamlessly links GitHub issues to local development environments.
  • Automated Branching: Generates descriptive branch names based on issue titles and labels.
  • Contextual Prompting: Injects issue details into the new development session for immediate context.
  • Use Case: When you see a new bug report or feature request on GitHub, you can tell Claude to "start issue #123" and it will set up everything you need to begin coding.

Quick Start

Use the create-worktree-from-issue skill to start working on issue number 42.

Frequently Asked Questions about create-worktree-from-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a git worktree from a GitHub issue?

To create a git worktree from a GitHub issue, this Skill automates the setup by generating a dedicated worktree, a descriptive branch, and a tmux window pre-populated with the issue's context. It links the GitHub issue directly to your local development environment.

What do I need to set up a tmux window and branch for issue tracking?

You need the gh CLI and workmux installed to provision the environment. These dependencies handle retrieving the GitHub issue details and automating the tmux window creation alongside the new git worktree and branch.

How are branch names generated when starting work on a GitHub issue?

Branch names are generated automatically based on the GitHub issue's title and labels. This ensures your development branches remain descriptive and contextually linked to the specific bug report or feature request.

Can I inject GitHub issue details into a new tmux development session?

Yes, the Skill injects GitHub issue details directly into the new tmux session for immediate context. This contextual prompting ensures you have the necessary issue information available as soon as you begin coding.

What is the best way to isolate development tasks for separate GitHub issues?

The best way to isolate development tasks is by creating a dedicated git worktree for each GitHub issue. This approach maps issues to local environments, automatically setting up isolated branches and tmux windows.

Why use a git worktree for GitHub issue tracking instead of a standard branch?

Using a git worktree allows you to isolate work on specific issues without switching branches in your main directory. It creates a separate working tree and tmux window, keeping development tasks cleanly separated.