worktree-from-issue

Create a Git worktree with a new branch for GitHub issues.

Updated Feb 26, 2026

Search Tags:#git #development workflow #github #branching #worktree #issue tracking

Ready to run

npx skills add https://github.com/Thanhhuong0209/DLT-Normalization --skill worktree-from-issue

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: worktree-from-issue
Source: https://github.com/Thanhhuong0209/DLT-Normalization/tree/main/.claude/skills/worktree-from-issue
Command: npx skills add https://github.com/Thanhhuong0209/DLT-Normalization --skill worktree-from-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of setting up a dedicated development environment for addressing specific GitHub issues, ensuring a clean and isolated workflow.

Core Features & Use Cases

Automated Branching: Creates a new Git branch based on a predefined naming convention derived from issue details.
Worktree Setup: Establishes an isolated worktree for the new branch, preventing interference with the main codebase.
Development Environment Configuration: Initializes the development environment within the worktree, including necessary setup steps.
Use Case: When a bug is reported (e.g., issue #3562), this Skill can automatically create a new branch fix/3562-bug-description in a separate worktree, set up the development environment, and verify the issue exists on GitHub.

Quick Start

Use the worktree-from-issue skill to create a git worktree for issue fix/3562-clickhouse-drop-sync-perf.

Frequently Asked Questions about worktree-from-issue

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

FAQPage Schema

How do I create a git worktree for a specific GitHub 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.

What is the best way to automate branch naming from GitHub issues?▼

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.

How does a git worktree setup help with issue tracking and development workflow?▼

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.

Can I verify GitHub issue existence before creating a new branch?▼

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.

Do I need a specific branching convention to use a git worktree for issue implementation?▼

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.

Why use git worktree instead of branching directly in the main repository?▼

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.