Interact with Atlassian Jira from the command line using jira-cli.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionjira-cliExecute the skills CLI command in your project's root directory to begin installation:
Fetches jira-cli from code-and-sorts/awesome-copilot-agents and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate jira-cli. Access via /jira-cli in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
1
total installs
1
this week
474
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
474
stars
Interact with Atlassian Jira from the command line using jira-cli.
brew install ankitpokhrel/jira-cli/jira-cli (macOS) or download from releasesexport JIRA_API_TOKEN="your-token"jira init and follow prompts# List issues in current project
jira issue list
# List my assigned issues
jira issue list -a$(jira me)
# List issues by status
jira issue list -s"In Progress"
# List high priority issues
jira issue list -yHigh
# List issues with multiple filters
jira issue list -a$(jira me) -s"To Do" -yHigh --created week
# List issues with raw JQL
jira issue list -q "project = PROJ AND status = 'In Progress'"
# Plain text output for scripting
jira issue list --plain --columns key,summary,status --no-headers
# Interactive issue creation
jira issue create
# Create with all options specified
jira issue create -tBug -s"Login button not working" -b"Description here" -yHigh --no-input
# Create a story
jira issue create -tStory -s"Add user authentication" -yMedium
# Create with labels and components
jira issue create -tTask -s"Update dependencies" -lmaintenance -l"tech-debt" -Cbackend
# Create and assign to self
jira issue create -tBug -s"Fix crash on startup" -a$(jira me) --no-input
# View issue details
jira issue view ISSUE-123
# View with comments
jira issue view ISSUE-123 --comments 10
# View in plain text
jira issue view ISSUE-123 --plain
# Open issue in browser
jira open ISSUE-123
# Edit summary
jira issue edit ISSUE-123 -s"Updated summary"
# Edit description
jira issue edit ISSUE-123 -b"New description"
# Edit priority
jira issue edit ISSUE-123 -yHigh
# Add labels
jira issue edit ISSUE-123 -lnew-label
# Move issue to a new status
jira issue move ISSUE-123 "In Progress"
# Move with comment
jira issue move ISSUE-123 "Done" --comment "Completed the task"
# Move and set resolution
jira issue move ISSUE-123 "Done" -RFixed
# Assign to self
jira issue assign ISSUE-123 $(jira me)
# Assign to specific user
jira issue assign ISSUE-123 username
# Unassign
jira issue assign ISSUE-123 x
# Add a comment
jira issue comment add ISSUE-123 "This is my comment"
# Add comment from editor
jira issue comment add ISSUE-123
# Log time
jira issue worklog add ISSUE-123 "2h 30m"
# Log time with comment
jira issue worklog add ISSUE-123 "1d 4h" --comment "Completed feature implementation" --no-input
# Link two issues
jira issue link ISSUE-123 ISSUE-456 Blocks
# Unlink issues
jira issue unlink ISSUE-123 ISSUE-456
# Clone an issue
jira issue clone ISSUE-123 -s"Cloned: New summary"
# Delete an issue
jira issue delete ISSUE-123
# List epics
jira epic list
# List epics in table format
jira epic list --table
# Create an epic
jira epic create -n"Q1 Features" -s"Epic summary" -b"Epic description"
# Add issues to epic
jira epic add EPIC-1 ISSUE-123 ISSUE-456
# Remove issues from epic
jira epic remove ISSUE-123 ISSUE-456
# List sprints
jira sprint list
# List current/active sprint
jira sprint list --current
# List my issues in current sprint
jira sprint list --current -a$(jira me)
# Add issues to sprint
jira sprint add SPRINT_ID ISSUE-123 ISSUE-456
# List projects
jira project list
# List boards
jira board list
# List releases/versions
jira release list
# Open project in browser
jira open
# Get current username
jira me
# Show help
jira --help
jira issue --help
# Setup shell completion
jira completion bash # or zsh, fish, powershell
| Flag | Description |
|---|---|
--plain |
Plain text output (no interactive UI) |
--raw |
Raw JSON output |
--csv |
CSV output |
--no-input |
Skip interactive prompts |
-t, --type |
Issue type (Bug, Story, Task, Epic) |
-s, --summary |
Issue summary/title |
-b, --body |
Issue description |
-y, --priority |
Priority (Highest, High, Medium, Low, Lowest) |
-l, --label |
Labels (repeatable) |
-a, --assignee |
Assignee username |
-r, --reporter |
Reporter username |
-C, --component |
Component name |
-P, --parent |
Parent issue/epic key |
-q, --jql |
Raw JQL query |
--created |
Filter by creation date (-7d, week, month) |
--order-by |
Sort field |
--reverse |
Reverse sort order |
# Assign to self and move to In Progress
jira issue assign ISSUE-123 $(jira me)
jira issue move ISSUE-123 "In Progress"
# Log work and close
jira issue worklog add ISSUE-123 "4h" --no-input
jira issue move ISSUE-123 "Done" --comment "Completed" -RFixed
# View my current sprint tasks
jira sprint list --current -a$(jira me)
# Create bug
jira issue create -tBug -s"App crashes on login" -yHigh -lbug --no-input
# Note the returned issue key, then assign
jira issue assign BUG-123 $(jira me)
jira issue move BUG-123 "In Progress"
| Command | Use Case |
|---|---|
jira issue list --plain |
Script-friendly output |
jira issue list --raw |
JSON for parsing |
jira issue list --csv |
Export to spreadsheet |
jira init configuration--custom flag with field IDsMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
We added jira-cli from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
jira-cli fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Solid pick for teams standardizing on skills: jira-cli is focused, and the summary matches what you get after install.
jira-cli fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added jira-cli from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: jira-cli is focused, and the summary matches what you get after install.
We added jira-cli from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
jira-cli is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in jira-cli — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: jira-cli is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 26