A Jira workflow command for retrieving issues, analyzing their requirements, searching with JQL, adding comments, and changing status. Jira is a tool teams use to track software work and bugs.

Use it to inspect acceptance criteria and dependencies, find related issues, post progress updates, and move tickets through workflow states.

It keeps ticket review and progress updates in the development workflow, reducing the need to switch between the agent and Jira.

cmd_jira — Skill for Claude Code by majiang213

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add majiang213/OpenClaw-MAS --skill cmd_jira

Clone the repo

git clone --depth 1 https://github.com/majiang213/OpenClaw-MAS

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/majiang213/openclaw-mas/cmd_jira/github.svg)](https://agentmods.dev/skills/majiang213/openclaw-mas/cmd_jira)

Your own site

<a href="https://agentmods.dev/skills/majiang213/openclaw-mas/cmd_jira"><img src="https://agentmods.dev/badge/skills/majiang213/openclaw-mas/cmd_jira/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/majiang213/openclaw-mas/cmd_jira"><img src="https://agentmods.dev/badge/skills/majiang213/openclaw-mas/cmd_jira.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 816 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00031	$0.00816
Opus 5	$0.00015	$0.00408
Sonnet 5	$0.00006	$0.00163
Haiku 4.5	$0.00003	$0.00082

Measured 5d ago against content hash ad719a9f565e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

cmd_jira scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/cmd_jira/SKILL.md · 119 lines

How it starts

The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Project Path

The first argument is the project path. Before doing anything else:

Extract the project path from the first argument
Verify the path exists
Work within that directory for all file operations and shell commands

Jira Command

Interact with Jira tickets directly from your workflow — fetch tickets, analyze requirements, add comments, and transition status.

Usage

/jira get <TICKET-KEY>          # Fetch and analyze a ticket
/jira comment <TICKET-KEY>      # Add a progress comment
/jira transition <TICKET-KEY>   # Change ticket status
/jira search <JQL>              # Search issues with JQL

What This Command Does

Get & Analyze — Fetch a Jira ticket and extract requirements, acceptance criteria, test scenarios, and dependencies
Comment — Add structured progress updates to a ticket
Transition — Move a ticket through workflow states (To Do → In Progress → Done)
Search — Find issues using JQL queries

How It Works

`/jira get <TICKET-KEY>`

Fetch the ticket from Jira (via MCP jira_get_issue or REST API)
Extract all fields: summary, description, acceptance criteria, priority, labels, linked issues
Optionally fetch comments for additional context
Produce a structured analysis:

Ticket: PROJ-1234
Summary: [title]
Status: [status]
Priority: [priority]
Type: [Story/Bug/Task]

Requirements:
1. [extracted requirement]
2. [extracted requirement]

Acceptance Criteria:
- [ ] [criterion from ticket]

Test Scenarios:
- Happy Path: [description]
- Error Case: [description]
- Edge Case: [description]

Dependencies:
- [linked issues, APIs, services]

Recommended Next Steps:
- /plan to create implementation plan
- /tdd to implement with tests first

`/jira comment <TICKET-KEY>`

Summarize current session progress (what was built, tested, committed)
Format as a structured comment
Post to the Jira ticket

`/jira transition <TICKET-KEY>`

Fetch available transitions for the ticket
Show options to user
Execute the selected transition

Read the full file on GitHub · 119 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

5d ago First seen · 119 lines · 31 tokens per session scan A ad719a9f565e

Subscribe to this mod's changes

cmd_jira is a skill published in the GitHub repository majiang213/OpenClaw-MAS (5 stars, last pushed 5mo ago), licensed MIT. It adds 31 tokens to every session and 816 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

LLM Project management ai-agents developer-tools openclaw skills

notion

Notion API for creating and managing pages, databases, and blocks via curl. Search, create, update, and query Notion workspaces directly from the terminal.

moltis-org/moltis · 36 tokens

jira

Jira project management expert for issues, sprints, workflows, and reporting.

RightNow-AI/openfang · 17 tokens

linear-tools

Linear project management expert for issues, cycles, projects, and workflow automation.

RightNow-AI/openfang · 17 tokens

create-issue

Create a GitHub issue with a drafted title and body. Use when the user asks to "create an issue", "file an issue", "open an issue", "submit an issue", "report a bug", "file a bug report", "file a feature request", or "file a design proposal".

tobihagemann/turbo · 66 tokens

pick-next-issue

Fetch and rank open GitHub issues by community engagement, present the top 3 candidates, and plan implementation for the selected issue. Use when the user asks to "pick next issue", "next issue", "which issue should I work on", "top issues", "most popular issues", "prioritize issues", or "what should I work on next".

tobihagemann/turbo · 77 tokens

produck-feedback

Use when acting on real user feedback — you have a Produck feedback ticket or URL, or the user wants to fix something users complained about or build a feature users asked for. Pulls full feedback context through the Produck MCP and drives a feedback → aligned PRD → build loop. Triggers on "fix what users reported", a…

tryproduck/produck-skills · 90 tokens