Automated summary
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" →
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/git-worktree-management-for-jira-tickets-mma3jrdd/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/git-worktree-management-for-jira-tickets-mma3jrdd' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/git-worktree-management-for-jira-tickets-mma3jrdd/download' --output '.skill-downloads/git-worktree-management-for-jira-tickets-mma3jrdd/SKILL.md.part' && mv '.skill-downloads/git-worktree-management-for-jira-tickets-mma3jrdd/SKILL.md.part' '.skill-downloads/git-worktree-management-for-jira-tickets-mma3jrdd/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/git-worktree-management-for-jira-tickets-mma3jrdd/SKILL.md' && test -s '.skill-downloads/git-worktree-management-for-jira-tickets-mma3jrdd/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/ticket' && cp -R '.skill-downloads/git-worktree-management-for-jira-tickets-mma3jrdd' '.claude/skills/ticket'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/git-worktree-management-for-jira-tickets-mma3jrdd'openskills read 'git-worktree-management-for-jira-tickets-mma3jrdd'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/git-worktree-management-for-jira-tickets-mma3jrdd/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.