Use when handling Jira issues, sprints, boards, links, fields, worklogs, attachments, or users, or on any Jira intent without a key ("create/find a ticket", "pick a project"). Auto-triggers on Jira URLs and issue keys (PROJ-123). Also use when MCP Atlassian tools fail or are unavailable for Jira Ser

Jira Communication CLI scripts via uv run , all supporting help , json , quiet , debug . Auto Trigger On Jira URL or issue key (PROJ 123), pick by intent — each is one call: Intent Tool triage / work on ticket jira issue.py work KEY start QA review jira issue.py qa KEY QA fail follow up jira issue.py qa fail KEY field only lookup jira issue.py get KEY fields ... change status jira issue.py act KEY → jira transition.py do audit / sibling discovery jira qa gather.py KEY Auth issues → jira setup.py . Anti pattern: get + comment list — use the matching verb. Scripts Under ${CLAUDE SKILL DIR}/scripts/{core,workflow,utility}/ . Core : jira issue.py , jira search.py , jira worklog.py , jira attachment.py , jira setup.py , jira validate.py Workflow : jira create.py , jira transition.py , jira comment.py , jira move.py , jira sprint.py , jira board.py , jira version.py , tempo account.py Utility : jira user.py , jira fields.py , jira link.py , jira weblink.py , jira worklog query.py , jira watchers.py , jira qa gather.py Execution Style Run directly. Scripts report ✓ / ✗ . Destructive ops: dry run . Global flags before subcommand: jira issue.py json get PROJ 123 . Basic Usage Transitions : list shows each transition's id and what its screen requires; pass the id to do — a name or a target status is not always unique, and an ambiguous one is refused rather than guessed. Terminal transitions : pass resolution <value ( Done , Won't do ); if rejected ("cannot be set"), retry without it — references/intent verbs.md . Versions : read references/versions.md before jira version.py . Mentions : posting commands verify [~username] (miss → suggestions); get / work print usernames ( references/fields and users.md ). Related Skills jira syntax : descriptions/comments use Jira wiki markup, not Markdown. No editorializing State what happened, not how good it is — references/no editorializing.md . References references/jql quick reference.md , references/jql cookbook.md references/multi profile.md — profile references/troubleshooting.md — auth, 401/403 references/issue editing.md — edit, delete, clear fields, fields json references/creation.md — create, parent , fields, admin scope ( project , tempo account.py ) references/comments.md — edit, delete, lint, body via references/worklog.md — started , ranges, tempo account , delete references/attachments.md — upload, download references/links.md — links references/agile.md — sprints/boards references/no editorializing.md — no self praise references/fields and users.md — custom field IDs, users, issue types references/watchers.md — watch, subscribe, list watchers references/versions.md — fix/affects versions, releases, version CRUD references/qa gather.md — audit bundle (siblings, prose URLs) references/intent verbs.md — work / qa / qa fail / act , exact transition names Authentication Cloud: JIRA URL + JIRA USERNAME + JIRA API TOKEN . Server/DC: JIRA URL + JIRA PERSONAL TOKEN . Config via ~/.env.jira or ~/.jira/profiles.json .

jira-communication