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 starting work on a new Jira ticket or cleaning up after completing one.
When working on tasks not tracked in Jira or when needing custom branch naming beyond the convention.
Security analysis
CautionThe 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.
- •Uses Bash tool to execute git commands and potentially remove worktrees, which could be destructive if misused.
Examples
start TDE-1234cleanup TDE-1234cleanupname: 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:
- Parse ticket ID from URL or direct input
- Fetch ticket details via Atlassian MCP
- Generate branch name:
feat/TDE-XXXX-short-description - Check for existing branch/worktree
- Create worktree from origin/main
- Copy .env and run npm install
- Move ticket to "In Development" status if not already
- Provide summary with next steps
Cleanup Workflow
See cleanup.md for detailed instructions.
Quick overview:
- List worktrees if no ticket specified
- Find matching worktree
- Check for uncommitted changes (warn if found)
- Check if branch is merged
- Remove worktree
- Optionally delete local branch
- 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
- "Optimize Lytics Tag Loading" →
Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.