Jira CLI
Command reference for driving Jira issues, sprints, and epics via the jira-cli tool
Test report
- Verdict
- Works with setup
- Score
- Tested
- Jul 21, 2026
- Environment
- Claude Code 2.x (agent harness)
- Upstream re-checked
- Aug 10, 2026 · 424fcd9
Fetched SKILL.md via raw GitHub; it is a single-file command reference (no bundled scripts/references, nothing to spot-check for broken paths). Frontmatter parses with name+description; only install command is `brew install ankitpokhrel/jira-cli/jira-cli` — no curl|sh, base64, or injection text. Cloned into a temp HOME and confirmed it copies to .claude/skills/jira-cli/SKILL.md cleanly. Could NOT measure output: `which jira` returned not-found, JIRA_API_TOKEN is unset, and there is no Jira instance, so every command (jira init, issue list/create/move, etc.) is unrunnable — an artifact would only restate the skill's syntax. Trigger phrasings: SHOULD — "Create a Jira bug for the login crash and assign it to me", "List my in-progress issues in the current sprint", "Move PROJ-42 to Done and log 2 hours" (all YES); should NOT — "Set up a Jira webhook to notify Slack on issue updates" (webhook/admin config, not jira-cli — NO), "Write a Confluence page documenting our release process" (Confluence, not Jira — NO). Docs match real jira-cli command/flag names; Compatibility and Limitations sections are honest.
Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works
- Installs cleanly 5/5
- Triggers reliably 5/5
- Output vs. baseline 5/10
- Docs & honesty 5/5
What Jira CLI does
A command reference that teaches Claude the correct ankitpokhrel/jira-cli syntax for creating, listing, viewing, editing, transitioning, assigning, and commenting on Jira issues, plus managing epics, sprints, boards, and worklogs. Triggers when the user asks to work with Jira tickets, issues, sprints, or project work items from the command line. Requires the jira-cli binary installed and configured via jira init with a JIRA_API_TOKEN.
How to install Jira CLI
git clone --depth 1 https://github.com/Code-and-Sorts/awesome-copilot-agents.git /tmp/jira-cli-src
mkdir -p ~/.claude/skills
cp -R /tmp/jira-cli-src/skills/jira-cli ~/.claude/skills/jira-cli
# Runtime deps (skill is just a command reference — the CLI does the work):
# brew install ankitpokhrel/jira-cli/jira-cli # macOS, or grab a release binary
# export JIRA_API_TOKEN="your-atlassian-api-token"
# jira init # interactive: pick Cloud/Server, project, board
# Needs a reachable Jira instance; without it none of the commands run.
Skills live in ~/.claude/skills/ (global) or .claude/skills/
(per-project). Restart Claude Code after installing.
Commands — how to trigger Jira CLI
-
/jira-cliCommand reference for driving Jira issues, sprints, and epics via the jira-cli tool
It also activates on plain-language prompts like these:
-
Create a Jira ticket for this bug -
List all issues in the current sprint -
Transition this Jira issue to In Review
Frequently asked questions
- Is the Jira CLI skill free?
- Yes. The skill itself is free from Code-and-Sorts/awesome-copilot-agents. SkillProof publishes the install command and an independent test verdict at no cost.
- Does Jira CLI work with Claude Code?
- We tested it with Claude Code 2.x (agent harness) on Jul 21, 2026. Verdict: Works with setup. Fetched SKILL.md via raw GitHub; it is a single-file command reference (no bundled scripts/references, nothing to spot-check for broken paths). Frontmatter parses with name+description; only install command is `brew install ankitpokhrel/jira-cli/jira-cli` — no curl|sh, base64, or injection text. Cloned into a temp HOME and confirmed it copies to .claude/skills/jira-cli/SKILL.md cleanly. Could NOT measure output: `which jira` returned not-found, JIRA_API_TOKEN is unset, and there is no Jira instance, so every command (jira init, issue list/create/move, etc.) is unrunnable — an artifact would only restate the skill's syntax. Trigger phrasings: SHOULD — "Create a Jira bug for the login crash and assign it to me", "List my in-progress issues in the current sprint", "Move PROJ-42 to Done and log 2 hours" (all YES); should NOT — "Set up a Jira webhook to notify Slack on issue updates" (webhook/admin config, not jira-cli — NO), "Write a Confluence page documenting our release process" (Confluence, not Jira — NO). Docs match real jira-cli command/flag names; Compatibility and Limitations sections are honest.
- What is the Jira CLI SkillProof Score?
- 8.0/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 5/10, docs & honesty 5/5.
- How do I install Jira CLI?
- Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
- Can I use Jira CLI with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
- The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.