jira-cli: Command-Line Jira Management

Use jira-cli when interacting with Jira. Assume jira-cli already installed.

Setup: If JIRA_API_TOKEN is not set, source the setup script first: source ./jira-cli/scripts/jira_cli_setup.sh — this loads the token from the macOS keychain (or prompts to create one).

Project flag: Always use -p PROJ to specify project explicitly (don’t rely on defaults)

Non-interactive flags: These are critical for agent usage — without them commands will hang:

• Always add --plain to list/view commands (prevents interactive TUI)
• Always add --no-input to create/edit commands (prevents interactive prompts)

When to Use

Use for: Reading issues, querying (status/priority/assignee filters), creating/updating issues, adding comments, closing after work complete

Ask user for web UI: Attachments/images, visual board operations (can’t do from CLI)

Core Pattern: Work on Issue

jira issue view -p PROJ PROJ-123              # Read requirements
jira issue assign PROJ-123 $(jira me)         # Assign to user
# ... implement ...
jira issue comment add PROJ-123 "Fixed in $(git rev-parse --short HEAD)"
jira issue move PROJ-123 "Done"               # Close when complete

Efficient Extraction

Extract only needed fields to minimize context usage:

# Get specific fields only
jira issue view -p PROJ PROJ-123 --raw | jq -r '.fields.status.name'

# List keys for iteration
jira issue list -p PROJ --plain --no-headers --columns KEY

When to Load Detailed Guide

Load jira-cli reference guide for:

• Command syntax and flags
• Query patterns and JQL filtering
• Output format options
• User intent → command mapping
• Git integration patterns

Workspace Convention

All temporary output (evals, benchmarks, scratch files) goes in the workspace/ directory inside this skill's directory. The */workspace/ pattern is gitignored.