Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Interact with Jira using the jira-cli tool. Search, create, view, edit, and transition issues; manage epics and sprints; add comments and worklogs. Use when working with Jira tickets, backlogs, or project management tasks.
.claude/skills/dicklesworthstone-jira/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | 49% | 0% |
| case-02 | ✗→✓ | ▲ Improved | 161% | 0% |
| case-03 | ✗→✓ | ▲ Improved | 136% | 0% |
| case-11 | ✗→✓ | ▲ Improved | 126% | 0% |
| case-13 | ✗→✓ | ▲ Improved | 149% | 0% |
Interactive Jira command line tool for managing issues, epics, sprints, and more.
Install jira-cli:
bash# macOS (Homebrew) brew install jira-cli # Or download from releases # https://github.com/ankitpokhrel/jira-cli/releases
bashexport JIRA_API_TOKEN="your-api-token"
Add to your shell config (~/.bashrc, ~/.zshrc, etc.) to make it persistent.
bashjira init
Follow the prompts to configure:
https://yourcompany.atlassian.net)For on-premise installations, you may need to set:
bashexport JIRA_AUTH_TYPE="bearer" # or "basic"
bash# List recent issues (interactive) jira issue list # List issues created in last 7 days jira issue list --created -7d # List issues by status jira issue list -s "To Do" jira issue list -s "In Progress" jira issue list -s "Done" # List issues by priority jira issue list --priority High # List issues by assignee jira issue list --assignee $(jira me) # List issues by reporter jira issue list --reporter $(jira me) # List issues by label jira issue list --label backend # List issues by project jira issue list --project PROJKEY # Plain output (non-interactive) jira issue list --plain # JSON output (for parsing) jira issue list --raw # CSV output jira issue list --csv # Complex query: High priority, assigned to me, in To Do, created this month jira issue list --priority High --assignee $(jira me) -s "To Do" --created month --label backend
| Flag | Description | Example | |------|-------------|---------| | -s, --status | Filter by status | -s "In Progress" | | -y, --priority | Filter by priority | --priority High | | -l, --label | Filter by label | -l backend | | -a, --assignee | Filter by assignee | -a $(jira me) | | -r, --reporter | Filter by reporter | -r $(jira me) | | --created | Filter by creation date | --created -7d, --created month | | --updated | Filter by update date | --updated -7d | | -p, --project | Filter by project | -p PROJKEY | | --type | Filter by issue type | --type Bug |
bash# View issue details in terminal jira issue view ISSUE-123 # View without pager jira issue view ISSUE-123 --no-pager # View in browser jira issue view ISSUE-123 --web
bash# Interactive creation (prompts for all fields) jira issue create # Create with summary only jira issue create "Fix login bug" # Create with type and summary jira issue create --type Bug "Fix login bug" # Create with all fields jira issue create \ --type Bug \ --summary "Fix login bug" \ --description "Users cannot login after update" \ --priority High \ --assignee "$(jira me)" \ --label backend,auth \ --project PROJKEY
bash# Interactive edit (opens in editor) jira issue edit ISSUE-123 # Edit summary jira issue edit ISSUE-123 --summary "New summary" # Edit description jira issue edit ISSUE-123 --description "Updated description" # Edit priority jira issue edit ISSUE-123 --priority High # Change assignee jira issue edit ISSUE-123 --assignee "$(jira me)" # Add labels jira issue edit ISSUE-123 --label backend,bug
bash# Interactive transition (choose from available transitions) jira issue transition ISSUE-123 # Transition to specific status jira issue transition ISSUE-123 "In Progress" jira issue transition ISSUE-123 "Done" jira issue transition ISSUE-123 "In Review"
bash# Add comment jira issue comment add ISSUE-123 "This needs more testing" # Add comment with markdown jira issue comment add ISSUE-123 "**Note:** This is a priority issue." # List comments jira issue comment list ISSUE-123 # Edit comment jira issue comment edit ISSUE-123 "Comment ID" "Updated comment" # Delete comment jira issue comment delete ISSUE-123 "Comment ID"
bash# Add worklog jira issue worklog add ISSUE-123 --time "2h" --message "Fixed the bug" # Add worklog with specific time jira issue worklog add ISSUE-123 --time "1d 2h 30m" --message "Implementation" # List worklogs jira issue worklog list ISSUE-123 # Delete worklog jira issue worklog delete ISSUE-123 "Worklog ID"
bash# List epics jira epic list # List epics in plain mode jira epic list --plain # Create epic jira epic create \ --name "Authentication System" \ --summary "Implement OAuth2 authentication" \ --description "Add OAuth2 login flow" # View epic details jira epic view EPIC-123 # List issues in epic jira epic list EPIC-123 # Add issues to epic jira issue edit ISSUE-123 --epic EPIC-123
bash# List sprints jira sprint list # List active sprint issues jira sprint list --state active # List issues in sprint jira sprint list SPRINT-123 # Start sprint jira sprint start SPRINT-123 # Close sprint jira sprint close SPRINT-123
bash# List projects jira project list # View project details jira project view PROJKEY
bash# Get current user info jira me # Get current user key jira me --key # Use in other commands jira issue list --assignee "$(jira me)"
bash# Jira Query Language (JQL) search jira issue list --query "project = PROJKEY AND status = 'In Progress'" # Complex JQL jira issue list --query 'project = PROJKEY AND assignee = currentUser() AND priority = High' # JQL with date range jira issue list --query "created >= -30d AND project = PROJKEY"
In interactive mode:
j/k/h/l - Navigatev - View issue detailsm - Transition issueENTER - Open in browserc - Copy issue URLCTRL+k - Copy issue keyCTRL+r or F5 - Refreshq / ESC / CTRL+c - Quit? - HelpUse different config files:
bash# Use specific config jira issue list --config ~/jira-configs/project1.yaml # Or set environment variable JIRA_CONFIG_FILE=~/jira-configs/project1.yaml jira issue list
bashjira issue list --assignee "$(jira me)" -s "In Progress" --created -7d
bashjira issue list -s "To Do" --priority High
bashjira sprint list --state closed jira issue list --sprint SPRINT-123 -s Done
bashjira issue transition ISSUE-123 "In Progress" jira issue view ISSUE-123
bashjira issue transition ISSUE-123 "Done" jira issue worklog add ISSUE-123 --time "1h" --message "Completed task"
1h (hour), 1d (day), 1w (week), 1m (month)-7d (7 days ago), month (this month), week (this week)-s "In Progress"| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-01 | fail→pass | 11,788 | 3,511 | -70% | 1 | 1 | 0% | 1,915 | 2,844 | +49% | 0 | 0 | — |
case-02 | fail→pass | 5,490 | 3,026 | -45% | 1 | 1 | 0% | 1,024 | 2,672 | +161% | 0 | 0 | — |
case-03 | fail→pass | 7,018 | 4,500 | -36% | 1 | 1 | 0% | 1,190 | 2,805 | +136% | 0 | 0 | — |
case-04 | pass→pass | 11,041 | 7,095 | -36% | 1 | 1 | 0% | 2,096 | 3,334 | +59% | 0 | 0 | — |
case-05 | pass→pass | 7,534 | 1,335 | -82% | 1 | 1 | 0% | 1,179 | 2,333 | +98% | 0 | 0 | — |
case-06 | pass→pass | 5,827 | 1,703 | -71% | 1 | 1 | 0% | 996 | 2,361 | +137% | 0 | 0 | — |
case-07 | pass→pass | 7,898 | 2,762 | -65% | 1 | 1 | 0% | 1,382 | 2,563 | +85% | 0 | 0 | — |
case-08 | pass→pass | 9,057 | 3,526 | -61% | 1 | 1 | 0% | 1,583 | 2,731 | +73% | 0 | 0 | — |
case-09 | pass→pass | 7,914 | 2,516 | -68% | 1 | 1 | 0% | 1,361 | 2,529 | +86% | 0 | 0 | — |
case-10 | pass→pass | 8,997 | 3,519 | -61% | 1 | 1 | 0% | 1,497 | 2,606 | +74% | 0 | 0 | — |
case-11 | fail→pass | 6,830 | 2,919 | -57% | 1 | 1 | 0% | 1,138 | 2,574 | +126% | 0 | 0 | — |
case-12 | pass→pass | 9,223 | 2,308 | -75% | 1 | 1 | 0% | 1,210 | 2,415 | +100% | 0 | 0 | — |
case-13 | fail→pass | 6,088 | 2,685 | -56% | 1 | 1 | 0% | 968 | 2,415 | +149% | 0 | 0 | — |
case-19 | fail→pass | 7,544 | 2,497 | -67% | 1 | 1 | 0% | 1,400 | 2,548 | +82% | 0 | 0 | — |
case-14 | pass→pass | 9,504 | 2,710 | -71% | 1 | 1 | 0% | 1,578 | 2,431 | +54% | 0 | 0 | — |
case-15 | fail→pass | 10,309 | 2,626 | -75% | 1 | 1 | 0% | 1,701 | 2,563 | +51% | 0 | 0 | — |
case-16 | fail→pass | 11,787 | 1,590 | -87% | 1 | 1 | 0% | 1,771 | 2,321 | +31% | 0 | 0 | — |
case-17 | pass→pass | 8,637 | 1,823 | -79% | 1 | 1 | 0% | 1,304 | 2,440 | +87% | 0 | 0 | — |
case-18 | pass→pass | 8,378 | 2,105 | -75% | 1 | 1 | 0% | 1,304 | 2,386 | +83% | 0 | 0 | — |
case-20 | fail→pass | 11,305 | 4,587 | -59% | 1 | 1 | 0% | 1,998 | 2,823 | +41% | 0 | 0 | — |
case-21 | pass→pass | 6,715 | 8,432 | +26% | 1 | 1 | 0% | 1,411 | 3,697 | +162% | 0 | 0 | — |
case-22 | pass→pass | 6,946 | 4,963 | -29% | 1 | 1 | 0% | 1,251 | 2,966 | +137% | 0 | 0 | — |
case-23 | pass→pass | 9,980 | 6,789 | -32% | 1 | 1 | 0% | 1,663 | 3,330 | +100% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 23 cases were attempted. The headline lift of +39 percentage points is the difference between those two pass rates over the 23 comparable cases.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.