Git worktree + JIRA-style branch

Use this skill when starting new work that should live in its own worktree and branch.

Naming convention

• •Worktree path (lowercase kebab): {repo}-{jira-ticket-lower}-{work-description}
  • •Example: email-kat-1376-use-immutable-ids
• •Branch (slash, not hyphen): {JIRA-TICKET}/{work-description} — use a slash between ticket and description (e.g. KAT-1318/create-trkd-msg-evnt). Do not use KAT-1318-create-trkd-msg-evnt; the slash form is required for the git commit prehook (XXX-0000/description shape).
  • •Example: KAT-1376/use-immutable-ids
• •Base: Create the branch from origin/master.

When to use

• •User asks for a new worktree or branch for a JIRA ticket.
• •User says they like "new work" in a new worktree with kebab-style name and JIRA-style branch.
• •Starting implementation for a ticket (e.g. KAT-1376, KAT-1318).

Instructions

1. •

   Resolve repo and ticket: From context, get the repo name (e.g. email), the JIRA ticket (e.g. KAT-1376), and a short work description (e.g. use-immutable-ids). Use kebab-case for the description.

2. •

   Worktree path: Build the worktree path as {repo}-{ticket-lower}-{description} and place it as a sibling of the main repo.

   • •Example: repo at /Users/you/Projects/email → worktree at /Users/you/Projects/email-kat-1376-use-immutable-ids
3. •

   Branch name: Always {TICKET}/{description} with a slash (never hyphen). Matches prehook expectation XXX-0000/description.

   • •Example: KAT-1376/use-immutable-ids, KAT-1318/create-trkd-msg-evnt
4. •

   Create worktree and branch: Use the slash-form branch name from the start.

   bash

   cd /path/to/repo
   git fetch origin
   git worktree add ../{worktree-name} -b {TICKET}/{description} origin/master
   

5. •

   Confirm: Tell the user the worktree path and branch so they can open it in Cursor or run commands there.

Examples

References

• •Cursor docs: Skill directories — skills can live in ~/.cursor/skills/ or ~/.claude/skills/.