worktree-from-issue

Create a git worktree and per-issue branch for a GitHub issue.

5.7k|578|Updated Jan 26, 2022
One-click install
npx skills add https://github.com/dlt-hub/dlt --skill worktree-from-issue-dlt-hub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktree-from-issue
Source: https://github.com/dlt-hub/dlt/tree/main/.claude/skills/worktree-from-issue
Command: npx skills add https://github.com/dlt-hub/dlt --skill worktree-from-issue-dlt-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Isolate work and streamline issue-focused development by automatically provisioning a dedicated git worktree and a new branch per GitHub issue.

Core Features & Use Cases

  • Create an isolated worktree to implement fixes or features for a specific issue, reducing context switching.
  • Validate branch naming conventions and extract issue metadata from provided arguments.
  • Sync with the latest development baseline by fetching origin/devel before creating the worktree.
  • Verify and report the worktree status, branch name, and related issue details for traceability.

Quick Start

Provide a valid argument like fix/1234-description to create and switch to a dedicated per-issue git worktree.

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?

You can create an isolated git worktree by providing a valid argument such as fix/1234-description. The tool parses this input, validates the branch name, verifies the GitHub issue, and automatically provisions a dedicated per-issue worktree synced with origin/devel.

What is the benefit of using a per-issue git worktree for feature development?

A per-issue git worktree isolates work for a specific GitHub issue, reducing context switching. It provisions a dedicated directory and branch, allowing you to implement fixes or features simultaneously without stashing changes in your main development environment.

How do I automatically validate branch naming conventions when creating a worktree?

You can automatically validate branch naming conventions by passing a structured argument like fix/1234-description to the tool. It parses the provided arguments to extract issue metadata and validates the branch name before creating the isolated git worktree.

Do I need the GitHub CLI to create an issue-scoped git worktree?

Yes, you need the GitHub CLI installed because the tool uses it for issue verification. It checks the existence of the GitHub issue and extracts relevant metadata to ensure the created worktree and branch are properly scoped to the correct issue.

How do I sync my new git branch with the latest development baseline before starting work?

The tool automatically syncs with the latest development baseline by fetching origin/devel before creating the worktree. This ensures your isolated per-issue branch is built on top of the most recent project changes and avoids integration conflicts.

What is the best way to isolate issue-focused development work from my main git repository?

Using a per-issue git worktree is the best way to isolate issue-focused development. It automatically creates a dedicated branch and working directory linked to your repository, ensuring traceability and preventing cross-contamination between concurrent feature implementations.