explainx.ainewsletter3.4k
Productivity

jira-cli▌

code-and-sorts/awesome-copilot-agents · updated Jun 2, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/code-and-sorts/awesome-copilot-agents --skill jira-cli
0 commentsdiscussion
summary

Interact with Atlassian Jira from the command line using jira-cli.

skill.md

Jira CLI

Interact with Atlassian Jira from the command line using jira-cli.

When to Use

  • User asks to create, view, edit, or search Jira issues/tickets
  • User needs to transition issues through workflow states (To Do → In Progress → Done)
  • User wants to manage sprints, epics, or boards
  • User needs to assign issues, add comments, or log work time
  • User asks about their current tasks or sprint progress

Prerequisites

  1. Install jira-cli: brew install ankitpokhrel/jira-cli/jira-cli (macOS) or download from releases
  2. Set API token: export JIRA_API_TOKEN="your-token"
  3. Initialize: jira init and follow prompts

Issue Commands

List Issues

# 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

Create Issues

# 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 Issues

# 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 Issues

# 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

Transition Issues

# 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 Issues

# 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

Comments

# Add a comment
jira issue comment add ISSUE-123 "This is my comment"

# Add comment from editor
jira issue comment add ISSUE-123

Work Logging

# 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 & Clone Issues

# 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

Epic Commands

# 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

Sprint Commands

# 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

Project & Board Commands

# List projects
jira project list

# List boards
jira board list

# List releases/versions
jira release list

# Open project in browser
jira open

Utility Commands

# Get current username
jira me

# Show help
jira --help
jira issue --help

# Setup shell completion
jira completion bash  # or zsh, fish, powershell

Common Flags

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

Common Workflows

Start Working on an Issue

# Assign to self and move to In Progress
jira issue assign ISSUE-123 $(jira me)
jira issue move ISSUE-123 "In Progress"

Complete an Issue

# Log work and close
jira issue worklog add ISSUE-123 "4h" --no-input
jira issue move ISSUE-123 "Done" --comment "Completed" -RFixed

Daily Standup Review

# View my current sprint tasks
jira sprint list --current -a$(jira me)

Create and Track a Bug

# 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"

Output Examples

Command Use Case
jira issue list --plain Script-friendly output
jira issue list --raw JSON for parsing
jira issue list --csv Export to spreadsheet

Limitations

  • Requires prior jira init configuration
  • Some features may vary between Jira Cloud and Server
  • Complex custom fields may require --custom flag with field IDs
  • Rate limits apply based on Jira instance configuration
how to use jira-cli

How to use jira-cli on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • ›Cursor installed and configured on your development machine
  • ›Node.js version 16.0+ with npm package manager (verify with node --version)
  • ›Active project directory or workspace where you want to add jira-cli
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/code-and-sorts/awesome-copilot-agents --skill jira-cli

The skills CLI fetches jira-cli from GitHub repository code-and-sorts/awesome-copilot-agents and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/jira-cli

Reload or restart Cursor to activate jira-cli. Access the skill through slash commands (e.g., /jira-cli) or your agent's skill management interface.

⚠

Security & Verification Notice

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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

Additional Resources

›View source code on GitHub›Skills CLI documentation›Learn more about Cursor›What are agent skills?

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases▌

User Story & Requirements Generation

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

Competitive Analysis

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

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

✓

Make data-driven prioritization decisions faster

Stakeholder Communication

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

Implementation Guide▌

Prerequisites

  • ›Claude Desktop or compatible AI client
  • ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • ›Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • ⚠Not validating competitive research—verify facts before sharing
  • ⚠Accepting user stories without involving engineering team
  • ⚠Over-relying on frameworks without qualitative judgment
  • ⚠Not customizing outputs to company culture and communication style
  • ⚠Skipping stakeholder validation of generated requirements

Best Practices▌

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • −Don't publish competitive analysis without fact-checking
  • −Don't finalize user stories without engineering review
  • −Don't make prioritization decisions solely on AI scoring
  • −Don't skip customer validation of generated requirements
  • −Don't ignore company-specific context and culture

💡 Pro Tips

  • ★Provide context: company goals, constraints, customer feedback
  • ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • ★Use skill for 70% generation + 30% customization to company needs

When to Use This▌

✓ 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.

Learning Path▌

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.5★★★★★26 reviews
  • ★★★★★Shikha Mishra· Dec 20, 2024

    We added jira-cli from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • ★★★★★Liam Brown· Dec 16, 2024

    jira-cli fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • ★★★★★Layla Agarwal· Nov 15, 2024

    Solid pick for teams standardizing on skills: jira-cli is focused, and the summary matches what you get after install.

  • ★★★★★Yash Thakker· Nov 11, 2024

    jira-cli fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • ★★★★★Liam Shah· Nov 7, 2024

    We added jira-cli from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • ★★★★★Evelyn Ndlovu· Oct 26, 2024

    Solid pick for teams standardizing on skills: jira-cli is focused, and the summary matches what you get after install.

  • ★★★★★Yusuf Desai· Oct 6, 2024

    We added jira-cli from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • ★★★★★Dhruvi Jain· Oct 2, 2024

    jira-cli is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • ★★★★★Anika Reddy· Sep 17, 2024

    Useful defaults in jira-cli — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • ★★★★★Oshnikdeep· Sep 13, 2024

    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

1 / 3