Worktree

Create isolated git worktrees for Jira tickets and tasks.

1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/mec07/claude_skills --skill worktree-mec07
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Worktree
Source: https://github.com/mec07/claude_skills/tree/main/stow/Worktree
Command: npx skills add https://github.com/mec07/claude_skills --skill worktree-mec07

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manages and isolates work by creating dedicated git worktrees for Jira tickets or generic tasks, reducing cross-branch interference and enabling parallel work.

Core Features & Use Cases

  • Create isolated worktrees for Jira tickets (e.g., DEV-1234) from origin/main
  • Support non-ticket tasks with ai/ branches and scratch-context integration
  • Spawn Engineer agents with full Jira context, track branches, PRs, and scratch files
  • Optional: copy IDE configuration to the worktree for faster local setup

Quick Start

Spin up a worktree for a Jira ticket or a descriptive task using /Worktree DEV-6182 or /Worktree add dark mode to dashboard.

Frequently Asked Questions about Worktree

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

FAQPage Schema
How do I create isolated git worktrees for Jira tickets to enable parallel development?

You can create isolated git worktrees for Jira tickets by spinning up a dedicated branch from origin/main using a ticket ID like DEV-1234, which reduces cross-branch interference and enables concurrent work.

Can I set up a git worktree for non-Jira tasks using a custom branch?

Yes, you can set up a git worktree for non-Jira tasks by using descriptive ai/ branches, which include scratch-context integration to support generic parallel development workflows.

How do automated agents work with git worktrees and Jira context?

Automated agents are spawned directly into the isolated worktree with full Jira context, allowing them to track branches, pull requests, and scratch files concurrently while executing tasks.

What is the best way to manage multiple parallel git branches without cross-branch interference?

The best way to manage parallel git branches without interference is to use dedicated worktrees for each task, providing isolated, auditable workspaces that prevent cross-branch contamination.

Does creating a git worktree copy IDE configuration for faster local setup?

Yes, creating a git worktree can optionally copy your IDE configuration into the new worktree directory, enabling faster local setup and immediate continuity for parallel development.