Jira Communication
CLI scripts via uv run. All support --help, --json, --quiet, --debug.
Auto-Trigger
On Jira URL or issue key (PROJ-123) → run jira-issue.py get. Auth issues → jira-setup.py.
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
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
uv run ${CLAUDE_SKILL_DIR}/scripts/core/jira-issue.py get PROJ-123
uv run ${CLAUDE_SKILL_DIR}/scripts/core/jira-search.py query "assignee = currentUser() AND status != Closed" -n 5 -f key,summary,status
uv run ${CLAUDE_SKILL_DIR}/scripts/core/jira-issue.py update PROJ-123 --assignee me --priority Critical
uv run ${CLAUDE_SKILL_DIR}/scripts/workflow/jira-comment.py add PROJ-123 "Comment text"
uv run ${CLAUDE_SKILL_DIR}/scripts/workflow/jira-transition.py do PROJ-123 "In Progress"
uv run ${CLAUDE_SKILL_DIR}/scripts/core/jira-worklog.py add PROJ-123 2h --comment "Work done"
uv run ${CLAUDE_SKILL_DIR}/scripts/workflow/jira-create.py issue PROJ "Summary" --type Task
uv run ${CLAUDE_SKILL_DIR}/scripts/core/jira-attachment.py add PROJ-123 screenshot.png
Related Skills
jira-syntax: For descriptions/comments. Jira uses wiki markup, not Markdown.
References
references/jql-quick-reference.md — when JQL goes beyond simple filtersreferences/jql-cookbook.md — when translating natural-language requests into JQLreferences/multi-profile.md — when using multiple Jira instances or --profilereferences/troubleshooting.md — when hitting auth, SSL, 401, 403, or connection failuresreferences/issue-editing.md — when using --fields-json, reporter changes, deletes, or movesreferences/creation.md — when creating with --parent, reporter, components, or custom fieldsreferences/comments.md — when editing, deleting, or listing commentsreferences/worklog.md — when using --started, date ranges, or jira-worklog-query.pyreferences/attachments.md — when uploading, downloading, or inspecting attachmentsreferences/links.md — when working with issue or web linksreferences/agile.md — when working with sprints, boards, or board --namereferences/fields-and-users.md — when looking up custom field IDs, users, or issue typesreferences/watchers.md — when the user asks to watch, subscribe, notify on, or list watchers of an issuereferences/versions.md — when the user asks about fix/affects versions, releases, or version CRUDreferences/qa-gather.md — when reviewing tickets in QA / "ready for review", or when a peer-review style runbook needs single-call context discovery
Authentication
Cloud: JIRA_URL + JIRA_USERNAME + JIRA_API_TOKEN. Server/DC: JIRA_URL + JIRA_PERSONAL_TOKEN. Config via ~/.env.jira or ~/.jira/profiles.json.
1---2name: jira-communication3description: Use when interacting with Jira issues - searching, creating, updating, moving, transitioning, commenting, logging work, downloading attachments, managing sprints, boards, issue links, web links, fields, or users. Auto-triggers on Jira URLs and issue keys (PROJ-123). Also use when MCP Atlassian tools fail or are unavailable for Jira Server/DC.4license: (MIT AND CC-BY-SA-4.0). See LICENSE-MIT and LICENSE-CC-BY-SA-4.05---67# Jira Communication89CLI scripts via `uv run`. All support `--help`, `--json`, `--quiet`, `--debug`.1011## Auto-Trigger1213On Jira URL or issue key (PROJ-123) → run `jira-issue.py get`. Auth issues → `jira-setup.py`.1415## Scripts1617Under `${CLAUDE_SKILL_DIR}/scripts/{core,workflow,utility}/`.1819**Core**: `jira-issue.py`, `jira-search.py`, `jira-worklog.py`, `jira-attachment.py`, `jira-setup.py`, `jira-validate.py`20**Workflow**: `jira-create.py`, `jira-transition.py`, `jira-comment.py`, `jira-move.py`, `jira-sprint.py`, `jira-board.py`, `jira-version.py`21**Utility**: `jira-user.py`, `jira-fields.py`, `jira-link.py`, `jira-weblink.py`, `jira-worklog-query.py`, `jira-watchers.py`, `jira-qa-gather.py`2223## Execution Style2425Run directly. Scripts report `✓`/`✗`. Destructive ops: `--dry-run`. Global flags before subcommand: `jira-issue.py --json get PROJ-123`.2627## Basic Usage2829```bash30uv run ${CLAUDE_SKILL_DIR}/scripts/core/jira-issue.py get PROJ-12331uv run ${CLAUDE_SKILL_DIR}/scripts/core/jira-search.py query "assignee = currentUser() AND status != Closed" -n 5 -f key,summary,status32uv run ${CLAUDE_SKILL_DIR}/scripts/core/jira-issue.py update PROJ-123 --assignee me --priority Critical33uv run ${CLAUDE_SKILL_DIR}/scripts/workflow/jira-comment.py add PROJ-123 "Comment text"34uv run ${CLAUDE_SKILL_DIR}/scripts/workflow/jira-transition.py do PROJ-123 "In Progress"35uv run ${CLAUDE_SKILL_DIR}/scripts/core/jira-worklog.py add PROJ-123 2h --comment "Work done"36uv run ${CLAUDE_SKILL_DIR}/scripts/workflow/jira-create.py issue PROJ "Summary" --type Task37uv run ${CLAUDE_SKILL_DIR}/scripts/core/jira-attachment.py add PROJ-123 screenshot.png38```3940## Related Skills4142**jira-syntax**: For descriptions/comments. Jira uses wiki markup, not Markdown.4344## References4546- `references/jql-quick-reference.md` — when JQL goes beyond simple filters47- `references/jql-cookbook.md` — when translating natural-language requests into JQL48- `references/multi-profile.md` — when using multiple Jira instances or `--profile`49- `references/troubleshooting.md` — when hitting auth, SSL, 401, 403, or connection failures50- `references/issue-editing.md` — when using `--fields-json`, reporter changes, deletes, or moves51- `references/creation.md` — when creating with `--parent`, reporter, components, or custom fields52- `references/comments.md` — when editing, deleting, or listing comments53- `references/worklog.md` — when using `--started`, date ranges, or `jira-worklog-query.py`54- `references/attachments.md` — when uploading, downloading, or inspecting attachments55- `references/links.md` — when working with issue or web links56- `references/agile.md` — when working with sprints, boards, or `board --name`57- `references/fields-and-users.md` — when looking up custom field IDs, users, or issue types58- `references/watchers.md` — when the user asks to watch, subscribe, notify on, or list watchers of an issue59- `references/versions.md` — when the user asks about fix/affects versions, releases, or version CRUD60- `references/qa-gather.md` — when reviewing tickets in QA / "ready for review", or when a peer-review style runbook needs single-call context discovery6162## Authentication6364Cloud: `JIRA_URL` + `JIRA_USERNAME` + `JIRA_API_TOKEN`. Server/DC: `JIRA_URL` + `JIRA_PERSONAL_TOKEN`. Config via `~/.env.jira` or `~/.jira/profiles.json`.
questnova502