Git Worktree Management for Jira Tickets

VerifiedCaution

Manages git worktrees for Jira ticket development. Creates worktrees from a main repo with auto-generated branch names, fetches ticket details via Jira, and optionally transitions the ticket to 'In Development'. Also handles cleanup of completed worktrees.

Sby Skills Guide Bot
DevelopmentIntermediate
606/2/2026
Claude Code
#git-worktrees#jira-integration#development-workflow#branch-management#ticket-management

Recommended for

Our review

Manages git worktrees for Jira tickets, creating branches from ticket summaries and cleaning up completed worktrees.

Strengths

  • Automates branch naming based on the Jira ticket title.
  • Integrates with Jira to update ticket status (e.g., move to 'In Development').
  • Creates worktree from origin/main, copies .env, and runs npm install.
  • Cleanup checks for uncommitted changes and branch merge status before removal.

Limitations

  • Only works with a specific repository path and naming convention.
  • Requires MCP Atlassian setup for Jira integration.
  • Does not handle complex merge or rebase workflows.
When to use it

When starting work on a new Jira ticket or cleaning up after completing one.

When not to use it

When working on tasks not tracked in Jira or when needing custom branch naming beyond the convention.

Security analysis

Caution
Quality score85/100

The skill requires Bash access to manage git worktrees, including creation and removal (e.g., 'git worktree remove'), which could lead to accidental data loss if not careful, but it is for a legitimate development workflow and no exfiltration or malicious activity is indicated.

Findings
  • Uses Bash tool to execute git commands and potentially remove worktrees, which could be destructive if misused.

Examples

Start a new ticket
start TDE-1234
Clean up a ticket worktree
cleanup TDE-1234
List existing worktrees
cleanup

name: ticket description: "[start <ticket>] [cleanup <ticket>] - Manages git worktrees for Jira tickets. Creates worktrees with auto branch naming, or cleans up completed worktrees." allowed-tools:

  • mcp__atlassian__getJiraIssue
  • mcp__atlassian__getTransitionsForJiraIssue
  • mcp__atlassian__transitionJiraIssue
  • Bash
  • Read

Ticket

Manages git worktrees for Jira ticket development.

Subcommands

| Command | Description | |---------|-------------| | /ticket start <ticket> | Create worktree for a Jira ticket | | /ticket cleanup [ticket] | Remove worktree (or list all if no ticket specified) |

Configuration

  • Main repo: ~/Vuori/cascade
  • Worktrees: ~/Vuori/cascade-worktrees
  • Jira cloud: vuoriclothing.atlassian.net

Start Workflow

See start.md for detailed instructions.

Quick overview:

  1. Parse ticket ID from URL or direct input
  2. Fetch ticket details via Atlassian MCP
  3. Generate branch name: feat/TDE-XXXX-short-description
  4. Check for existing branch/worktree
  5. Create worktree from origin/main
  6. Copy .env and run npm install
  7. Move ticket to "In Development" status if not already
  8. Provide summary with next steps

Cleanup Workflow

See cleanup.md for detailed instructions.

Quick overview:

  1. List worktrees if no ticket specified
  2. Find matching worktree
  3. Check for uncommitted changes (warn if found)
  4. Check if branch is merged
  5. Remove worktree
  6. Optionally delete local branch
  7. Provide summary with remaining worktrees

Branch Naming Rules

Convert ticket summary to kebab-case:

  • Lowercase, 3-5 words max
  • Remove filler words (the, a, an, for, to)
  • Examples:
    • "Optimize Lytics Tag Loading" → feat/TDE-1234-optimize-lytics-loading
    • "Fix Cart Mobile Layout Bug" → feat/TDE-1234-fix-cart-mobile-layout
Related skills