Jirac
Correct-syntax Jira CLI cheat sheet for the jirac Rust binary — no raw REST guesswork.
Test report
- Verdict
- Tested · Works
- Score
- Tested
- Jul 14, 2026
- Environment
- Claude Code 2.x (agent harness)
- Upstream re-checked
- Aug 10, 2026 · fa1f6b7
Asked for the exact commands to check status, standup, transition, and comment on an issue: unguided, the natural guess was `jira ... --to Done`; the skill's documented syntax is `jirac issue transition PROJ-123 'Done'` (positional, no --to) — the skill catches a real, verifiable CLI gotcha a generic guess gets wrong.
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 9/10
- Docs & honesty 5/5
What Jirac does
Teaches an agent to drive Jira entirely through the `jirac` CLI — listing, creating, transitioning, commenting on, bulk-editing, cloning, linking, and archiving issues, plus sprint lifecycle, worklogs, standup/sprint summaries, and MCP registration — instead of hand-rolling raw Jira REST calls. Triggers on any Jira issue-management request (list/create/transition/comment/sprint/standup) once the `jirac` binary is installed and authenticated via `jirac auth login`. The command reference is accurate down to CLI-specific quirks, such as `transition` taking a positional argument rather than a `--to` flag.
How to install Jirac
git clone https://github.com/mulhamna/jira-commands
cd jira-commands
mkdir -p ~/.claude/skills
cp -r clawhub/jirac ~/.claude/skills/jirac
Skills live in ~/.claude/skills/ (global) or .claude/skills/
(per-project). Restart Claude Code after installing.
Commands — how to trigger Jirac
-
/jiracCorrect-syntax Jira CLI cheat sheet for the jirac Rust binary — no raw REST guesswork.
It also activates on plain-language prompts like these:
-
List my assigned Jira issues in project PROJ using jirac please. -
Generate my daily standup summary from Jira with the jirac CLI. -
Transition PROJ-123 to Done and add a QA comment using jirac.
Frequently asked questions
- Is the Jirac skill free?
- Yes. The skill itself is free from mulhamna/jira-commands. SkillProof publishes the install command and an independent test verdict at no cost.
- Does Jirac work with Claude Code?
- We tested it with Claude Code 2.x (agent harness) on Jul 14, 2026. Verdict: Tested · Works. Asked for the exact commands to check status, standup, transition, and comment on an issue: unguided, the natural guess was `jira ... --to Done`; the skill's documented syntax is `jirac issue transition PROJ-123 'Done'` (positional, no --to) — the skill catches a real, verifiable CLI gotcha a generic guess gets wrong.
- What is the Jirac SkillProof Score?
- 9.6/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 9/10, docs & honesty 5/5.
- How do I install Jirac?
- 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 Jirac 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.