# Manage Jira Workflows from the CLI

Teams lose time switching between Jira screens and development tools. This skill guides Claude, Codex, and Claude Code through jira-cli commands for common issue, sprint, and epic work.

## Install

```bash
npx skillstore add code-and-sorts/jira-cli
```

## Metadata

- Status: approved
- Slug: code-and-sorts-jira-cli
- Version: 1.0
- Author version: 1.0
- Skillstore revision: r1
- Version status: invalid
- Tree hash: c9ff56af0eb4f94bc4340b434810a09002e29dc195ed7d232508880c7689e67f
- Author: Code-and-Sorts
- GitHub username: Code-and-Sorts
- License: MIT
- Repository: https://github.com/Code-and-Sorts/awesome-copilot-agents/tree/main/skills/jira-cli
- Ref: 02f077c174c5335e2f5d02ca15e77b70d9543e58
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 70
- Public page: https://skillstore.pages.dev/skills/code-and-sorts-jira-cli
- Manifest: https://skillstore.pages.dev/api/skills/code-and-sorts-jira-cli/manifest

## Capabilities

- List Jira issues by assignee, status, priority, JQL, and creation date.
- Create bugs, stories, tasks, labels, components, and self-assigned issues.
- View issues with comments, plain text output, and browser opening.
- Edit summaries, descriptions, priorities, labels, assignments, comments, worklogs, and workflow states.
- Manage epics, sprints, boards, projects, releases, and shell completion.

## Use Cases

- Review Assigned Work: List current Jira issues, filter by status or priority, and open the needed ticket details.
- Track Sprint Progress: Check active sprint issues, move work through statuses, and summarize blockers for standup.
- Coordinate Epics and Releases: List epics, attach issues, inspect releases, and export concise project progress summaries.

## Prompt Templates

### List My Open Issues

```
Show my Jira issues in the current project, grouped by status. Use plain text output when possible.
```

### Create a Bug

```
Create a high priority Jira bug for a login crash. Include a concise summary, reproduction notes, and a bug label.
```

### Plan Sprint Work

```
Find my current sprint issues, identify blockers from issue summaries and comments, and suggest the next three actions.
```

### Prepare Issue Cleanup

```
Search for high priority issues created this week, summarize them, and prepare safe update commands for my approval.
```

## Limitations

- Requires jira-cli installed and configured with jira init.
- Requires a valid JIRA\_API\_TOKEN and Jira account permissions.
- Custom fields may need explicit field IDs and custom options.
- Behavior can vary between Jira Cloud and Jira Server instances.

## Best Practices

- Confirm the active project and Jira site before creating or editing issues.
- Use plain text or CSV output for summaries and reports.
- Ask for explicit approval before deleting issues or closing work.

## Anti Patterns

- Do not run destructive commands without a clear issue key and user confirmation.
- Do not paste API tokens into prompts or ticket comments.
- Do not rely on default Jira project settings when multiple projects are configured.

## Security Audit

- Audited at: 2026-07-05T07:28:21.653\+00:00
- Summary: Most static alerts are markdown examples for jira-cli, not executable code embedded in the skill. Real residual risk comes from guiding an agent to run an external CLI that can read and mutate Jira data. No prompt injection or covert exfiltration intent was found.

## Stats

- Views: 295
- Downloads: 18
- Favorites: 0
- Popularity score: 0