jira-cli skill
✓ VerifiedExecute raw Jira CLI commands for managing issues, epics, and sprints via command line or automation scripts.
- GitHub stars
- 8
- Files
- 6
- Last commit
- Oct 28, 2026
- License
- MIT
- Allowed tools
- —
What does the jira-cli skill do?
jira-cli is an agent skill. Execute raw Jira CLI commands for managing issues, epics, and sprints via command line or automation scripts.
Summary generated from the skill's SKILL.md.
About the jira-cli skill
Managing Jira issues, epics, and sprints through direct command-line execution is what this skill enables for developers and automation engineers. It provides a way to run raw ankitpokhrel/jira-cli commands against Jira Cloud or on-premise instances, making it ideal for users who need specific JQL-style filtering or complex CRUD operations that standard curated skills might not cover. An agent should load this skill when a user explicitly requests literal jira CLI syntax or needs to drive bash and CI automation scripts.
To ensure successful operation, the tool relies on the jira binary being present on the system path and authenticated via jira init. When an agent uses this skill to produce data for further processing, it should include the --plain and --no-headers flags to generate parseable, tab-separated text output instead of interactive tables. This allows for reliable scripting of tasks like bulk assignments, auto-labeling, or adding worklogs without manual intervention.
What an agent can do with it
- 1Automate issue creationCreate a new bug report with specific priority and description without using the web interface.
- 2Perform bulk sprint updatesAdd a specific list of issue keys to an existing sprint.
- 3Extract parseable issue dataRetrieve a list of issues in a specific status to use in a bash loop.
- 4Manage worklogs and commentsAdd time tracking and a descriptive comment to a specific ticket.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the jira-cli skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the jira-cli skill in Plugin
/plugin marketplace add mgiovani/cc-arsenal /plugin install cc-arsenal@cc-arsenal-marketplace
Install the jira-cli skill in Claude Code
~/.claude/skills/jira-cli/SKILL.md
$ npx degit mgiovani/cc-arsenal/skills/jira-cli ~/.claude/skills/jira-cliInstall the jira-cli skill in Claude Code (project)
.claude/skills/jira-cli/SKILL.md
$ npx degit mgiovani/cc-arsenal/skills/jira-cli .claude/skills/jira-cliInstall the jira-cli skill in Codex
~/.agents/skills/jira-cli/SKILL.md
$ npx degit mgiovani/cc-arsenal/skills/jira-cli ~/.agents/skills/jira-cliInstall the jira-cli skill in Gemini CLI
~/.gemini/skills/jira-cli/SKILL.md
$ npx degit mgiovani/cc-arsenal/skills/jira-cli ~/.gemini/skills/jira-cliInstall the jira-cli skill in Claude.ai
npx degit mgiovani/cc-arsenal/skills/jira-cli jira-cli && zip -r jira-cli.zip jira-cli # claude.ai → Customize → Skills → + → Create skill → Upload a skill → jira-cli.zip
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachablemgiovani/cc-arsenal/skills/jira-cli is public and reachablegithub.com/mgiovani/cc-arsenal/tree/HEAD/skills/jira-cli ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-10-28github.com/mgiovani/cc-arsenal/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/mgiovani/cc-arsenal/blob/HEAD/skills/jira-cli/SKI ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/mgiovani/cc-arsenal/blob/HEAD/skills/jira-cli/SKI ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 132 linesgithub.com/mgiovani/cc-arsenal/blob/HEAD/skills/jira-cli/SKI ↗Pass
SKILL.md
View on GitHubJira CLI
Command reference and scripting patterns for jira-cli, the command-line tool for managing Jira issues, epics, and sprints without the web UI.
Prerequisites
Install with brew install ankitpokhrel/jira-cli/jira-cli, then run jira init once to authenticate.
These references assume jira on PATH is ankitpokhrel/jira-cli: a different tool can claim the same binary name. Before trusting any command below, run jira version once per session and confirm the output looks like this project (e.g. jira version 1.x.x with a Homepage: https://github.com/ankitpokhrel/jira-cli line). If it doesn't, stop and check which jira instead of guessing at flags.
For AI use, always add --plain (and usually --no-headers) to get parseable text output instead of the interactive table.
When to Use This Skill
Manual slash-command skill (/jira-cli): it does not auto-trigger on mentions of "jira" or "ticket". Invoke it directly for raw jira CLI commands (issues, epics, sprints) or scripting/automation. On tools that don't read Claude-Code frontmatter, disable-model-invocation is ignored: the /jira-cli phrasing itself is the manual-invocation signal there too.
Essential Commands
Curated top-7 for the most common operations. For anything else (filters, epic/sprint management, releases, output formats), load references/commands.md; don't try to recall the rest from memory.
# List recent issues (always use --plain for AI)
jira issue list --plain
# View issue details
jira issue view ISSUE-1 --plain
# Create an issue
jira issue create -tBug -s"Bug title" -yHigh -b"Description" --no-input
# Assign issue to yourself
jira issue assign ISSUE-1 $(jira me)
# Move issue to "In Progress"
jira issue move ISSUE-1 "In Progress"
# Add comment
jira issue comment add ISSUE-1 --comment "My comment"
# Add worklog
jira issue worklog add ISSUE-1 "2h" --comment "Implementation work"
Worked Examples
Confirm the CLI flavor before anything else:
$ jira version
jira version 1.5.1
Homepage: https://github.com/ankitpokhrel/jira-cli
A different jira version output (or a "command not found") means stop and resolve which jira before running any command from this skill.
Parse --plain output for scripting: columns are tab-separated, headers are on unless suppressed:
$ jira issue list -a$(jira me) -s"In Progress" --plain --no-headers --columns key,summary
PROJ-123 Fix login redirect loop
PROJ-124 Add rate limiting to API
jira issue list -a$(jira me) -s"In Progress" --plain --no-headers --columns key,summary | \
while IFS=$'\t' read -r key summary; do echo "Working: $key - $summary"; done
Create non-interactively and capture the new key from the URL jira-cli prints:
$ jira issue create -tBug -s"Login redirect loop" -yHigh --no-input
Issue created
https://your-domain.atlassian.net/browse/PROJ-125
key=$(jira issue create -tBug -s"Login redirect loop" -yHigh --no-input | grep -oE '[A-Z]+-[0-9]+$')
Bulk sprint add: list the keys with a live filter, then add only the keys the user confirmed (see Destructive operations):
jira issue list -s"Ready for Dev" --plain --columns key,summary --no-headers
jira sprint add SPRINT_ID PROJ-123
Destructive operations
Applies to delete, bulk transition/assign/edit, removing issues from a sprint, and anything that touches more than one issue. Copy this checklist and tick it off:
- [ ] 1. List the exact keys with a read-only query
- [ ] 2. Show the keys and get explicit confirmation
- [ ] 3. Run the command once per confirmed key
- Query read-only with the same filter the mutation would use, e.g.
jira issue list -s"Ready for Dev" --plain --columns key,summary --no-headers. - Show that exact list to the user and wait for an explicit yes. If the list changes or the user edits it, return to step 1. No answer means stop and report.
- Run the exact command for each confirmed key, e.g.
jira issue delete PROJ-123. Never pipe the query into the mutation (... | xargs jira issue delete): nothing reviews what the pipe actually receives.
How to Use This Skill
Load reference files on demand, don't pull all three into context for a single command.
1. Comprehensive Commands Reference
Load: references/commands.md
Detailed syntax for issue management (list, create, edit, assign, move, view, link, clone, delete, comments, worklog), epic management, sprint management, releases, and output-format options.
2. Common Workflow Examples
Load: references/workflows.md
Multi-command patterns: sprint planning, code review handoff, bug triage, epic tracking, incident response, backlog grooming, cross-team coordination.
3. Scripting and Automation
Load: references/scripting.md
Raw bash automation that isn't already a curated skill: bulk assignment, auto-labeling, CSV export, velocity/metrics calculation, CI/CD hooks (GitHub Actions, GitLab CI, Jenkins), error handling and rate-limiting patterns.
Resources
| Resource | Link |
|---|---|
| GitHub | https://github.com/ankitpokhrel/jira-cli |
| Installation guide | https://github.com/ankitpokhrel/jira-cli/wiki/Installation |
| FAQs | https://github.com/ankitpokhrel/jira-cli/discussions/categories/faqs |
Files in this skill
6jira-cli skill questions
How do I install the jira-cli skill in Claude Code?
Run npx degit mgiovani/cc-arsenal/skills/jira-cli ~/.claude/skills/jira-cli. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the jira-cli skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
How should an AI agent format Jira CLI output for parsing?
Always use the --plain flag, and ideally --no-headers, to receive parseable text output instead of interactive tables.