jiralisted

## What I do I act as an intelligent bridge between natural language and the Jira CLI. I allow you to find, read, update, transition, and comment on tickets. Crucially, I maintain state across conversation turns (remembering which ticket we are discussing) and ensure complex text is correctly formatted for Jira's rendering engine. ## When to use me Use this skill when: - You are asked to use Jira or jira-cli. - You need to **find** a ticket based on keywords, status, or assignee. - You need to **read** the details of a specific issue. - You need to **transition** a ticket (e.g., "Move this to Done"). - You need to **update** fields or **comment** on an issue. - The user references "tickets," "issues," "epics," or "sprints." ## Instructions ### 1. Context Retrieval & Management Before executing any Jira command, you must establish the "Active Issue." * **Check Memory**: Query `serena` or `openmemory` for a `JIRA_ISSUE` node linked to the current session via `DISCUSSING`. * **Check Environment**: Look for an issue key in the current git branch name (e.g., `feat/PROJ-123-login`). * **Search**: If no context exists, use JQL to find the issue. * **Persist**: Once an issue is identified/discussed, store it in memory immediately. * *Pattern*: `(Session) -[DISCUSSING]-> (JIRA_ISSUE {key: "PROJ-123"})` ### 2. Reading Issues (The JSON Rule) **NEVER** use `jira issue view` directly, as the output is often unstructured text. * **Command**: Use `jira issue list --raw` with a spe