# Jira Command Line

Searches, inspects, creates and updates Jira issues from the terminal.

- Repository: https://github.com/ankitpokhrel/jira-cli (6055 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-17
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add ankitpokhrel/jira-cli --skill jira-cli -g -a claude-code -y`
Codex: `npx skills add ankitpokhrel/jira-cli --skill jira-cli -g -a codex -y`
Cursor: `npx skills add ankitpokhrel/jira-cli --skill jira-cli -g -a cursor -y`
Gemini CLI: `npx skills add ankitpokhrel/jira-cli --skill jira-cli -g -a gemini-cli -y`

## Description

Use Jira-CLI to search, inspect, create, or update Jira issues and related project data. Covers machine-readable output, configuration metadata, command discovery, and safe execution.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Jira CLI

Use this skill when operating Jira through the `jira` command. Start with `jira --help`, then inspect the relevant command and subcommand help (for
example, `jira issue list --help`) before using them. The installed CLI's help is the source of truth for its available commands, flags, and syntax; it also
contains command-specific examples. This skill adds agent-oriented safety guidance and useful workflow patterns that may not be obvious from the flags.

## Prefer machine-readable output

List commands are interactive by default. When reading data programmatically, prefer an output format intended for parsing:

```sh
# JSON
jira issue list --raw

# Plain text, optionally selecting fields and omitting headers
jira issue list --plain --columns key,summary --no-headers

# CSV
jira issue list --csv
```

Use `--raw` when supported and JSON is needed. Otherwise, use `--plain` with `--columns` and `--no-headers` to minimize parsing ambiguity.

## Configuration and fields

The default configuration file is:

```text
$XDG_CONFIG_HOME/.jira/.config.yml
```

When `XDG_CONFIG_HOME` is unset, it is:

```text
~/.config/.jira/.config.yml
```

The configuration file can be used as a data source. It contains the configured project, issue types, and custom field definitions. In particular, inspect
`issue.types` and `issue.fields.custom` before constructing `create`, `edit`, or `--custom` commands.

Use `--config/-c` or `JIRA_CONFIG_FILE` to select another configuration file.

This metadata is created during `jira init` and, over time, can become out of sync with Jira. Refreshing the configuration with `jira init` changes local
configuration. NEVER do it without obtaining explicit confirmation first.

The rest: https://github.com/ankitpokhrel/jira-cli/blob/HEAD/skills/jira-cli/SKILL.md