Jira Cli

Organization

Code-and-Sorts

jira-cli

Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.

Overview

Publisher	Code-and-Sorts
Repository	`awesome-copilot-agents`
Skill name	`jira-cli`
Stars	580
Forks	96
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by Code-and-Sorts on GitHub. Read the source before you install it.

Installation

Install the Jira Cli AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/Code-and-Sorts/awesome-copilot-agents/tree/main/skills/jira-cli
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/Code-and-Sorts/awesome-copilot-agents.git /tmp/awesome-copilot-agents
mkdir -p .claude/skills
cp -r /tmp/awesome-copilot-agents/skills/jira-cli .claude/skills/jira-cli

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Jira Cli in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Jira Cli on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Jira Cli is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

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

Issue Commands

List Issues

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

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

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

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

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

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

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

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

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

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

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

bash
# List projects
jira project list

# List boards
jira board list

# List releases/versions
jira release list

# Open project in browser
jira open

Utility Commands

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

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

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

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

Create and Track a Bug

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

Frequently asked questions

What does the Jira Cli AI skill do?

Why use Jira Cli on TypingMind?

Because you install it once and use it with any model. Jira Cli is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Jira Cli in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Code-and-Sorts/awesome-copilot-agents/tree/main/skills/jira-cli. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Jira Cli?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Jira Cli?

As many as you like. As long as a model supports skills, you can use Jira Cli with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Jira Cli AI skill free?

Yes. It is published on GitHub by Code-and-Sorts under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Brainstorming

obra

CommunityPopular

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Executing Plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Using Superpowers

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

Context And Decisions

affaan-m

CommunityPopular

Govern stable domain context with a narrowly scoped CONTEXT.md when needed, and route hard-to-reverse decisions to ECC's existing architecture-decision-records skill. Use when domain terms require…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Jira CLI

When to Use

Prerequisites

Issue Commands

List Issues

Create Issues

View Issues

Edit Issues

Transition Issues

Assign Issues

Comments

Work Logging

Link & Clone Issues

Epic Commands

Sprint Commands

Project & Board Commands

Utility Commands

Common Flags

Common Workflows

Start Working on an Issue

Complete an Issue

Daily Standup Review

Create and Track a Bug

Output Examples

Limitations

Frequently asked questions

Related AI Skills

Set up your own AI workspace now