What problem does it solve? Long-running Claude sessions inside tmux all show generic window names, making it impossible to tell which pane holds which task. This Skill names the window after the Jira ticket or topic being worked on, so the status bar stays readable across many sessions. ## Core Features & Use Cases - Ticket-based naming: Extracts a ticket key (e.g. GTI-197) from the current git branch, fetches the Jira summary via the Atlassian MCP tool, and squeezes it into a short label like GTI-197 jira-optimizer. - Literal and topic naming: Applies a user-supplied name verbatim, or derives a 2-4 word kebab-case title from the session when no ticket exists. - Safe tmux plumbing: A bundled script targets $TMUX_PANE (Claude's own window, not the attached client's active window), preserves the leading status glyph, and sets @claude_base and @claude_autoname_done so hooks do not revert the name. - Use Case: You start work on branch feature/GTI-274-custom-domain-mapping and ask to tag the window; the window becomes ● GTI-274 domain-mapping after a quick confirmation. ## Quick Start Ask the assistant to rename this tmux window to the current Jira ticket, or say "rename this window to deploy-fix" to apply a literal name.
